Thanks for quick reply. I will check it and reply the status soon. Regards, George
On Tue, Nov 30, 2010 at 11:38 PM, John Adams <[email protected]> wrote: > On Mon, Nov 29, 2010 at 11:11 PM, Georgooty varghese > <[email protected]>wrote: > >> Dear Twitter, >> >> I wont be able to log in to twitter insecure using twitter(using curl >> command line tool, you disable this with -k/--insecure). But facebook has no >> problem. Why this? >> >> I think that client need a certifuication? Is it right? >> > > Twitter uses an EV Certificate issued by Verisign. Facebook uses a 3rd > party EV Certificate, which is not issued by Verisign. > Some versions of curl do not ship with a proper certificate chain. That's > why you're having issues verifying the certificate. > > The attached CA Bundle file will fix your issue. While it's 239K, you > really only need the CA and Intermediate certs in this file for Verisign. > You can remove the rest. > > This file gets loaded in your code with: > > curl_easy_setopt(m_hcURL, CURLOPT_CAINFO,"curl-ca-bundle.crt")); > > > Your hardware may also have additional dependencies on having an accurate, > real-time clock, depending on how you communicate with the API and what > level of verification you do on SSL certs. Make sure that's set correctly as > well. > > -j > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
