Check here:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/4e6a8b0c7d73d85
On Nov 17, 2:36 pm, Tim Haines tmhai...@gmail.com wrote:
Hi Marcel,
Thanks for following up on this. The bad cert responses I got were
inconsistent. Often it would work fine, so what
I've been having this same issue when connecting to https://api.twitter.com.
I would have thought that if it is a problem with my code, I would
always get this error. However, it is intermittent. Most times it
works, but a few times an hour I will get the error. Also, I never
have this problem
Ops has been trying to track down this problem for a while. They
confirmed that all servers have the correct cert. The current
hypothesis is that there are some rogue servers that are being load
balanced to that we don't expect to be accepting api.twitter.com
traffic that do not have the correct
On Nov 17, 2009, at 10:50 AM, David Dellanave wrote:
Could this be related to when an API request returns raw HTML like
the over-loaded page? That would be my first guess.
SSL/TLS negotiation happens much earlier in the transaction, so no,
raw HTML is not a cause of this.
-john
Hi Marcel,
Thanks for following up on this. The bad cert responses I got were
inconsistent. Often it would work fine, so what you've outlined here is one
theory that would explain it.
I think I'll switch back to twitter.com for this app, and look at using
api.twitter.com in a future update.
On Nov 15, 2009, at 1:16 PM, Tim Haines wrote:
Hi there,
I'm doing some dev work and I'm getting occasional ssl errors when
making calls against api.twitter.com/1. The most recent was posting
to favorites/create.
Is it possible some of the servers have bad certificates? Or is it
This could possibly be related,
I recently switched from using https://twitter.com to https://api.twitter.com
and found that the majority of my cURL calls (via php) to the api
started failing, although no other parts of my function changed.
Out of curiosity I changed it to
When you use HTTP over HTTPS you will never have trouble with (TLS)
certs because they
are never used for port 80 traffic.
On Sun, Nov 15, 2009 at 19:56, dean.j.robinson
dean.j.robin...@gmail.com wrote:
This could possibly be related,
I recently switched from using https://twitter.com to
