Hey guys, Is anyone else having issues replying to a tweet with their
applications?
I am receiving a HTTP 0 status response when I have set the
reply_to_id, or the tweet begins with a @username - however every
other API method is working fine, including a tweet without these two
variables.
I
Hi Chris,
HTTP does not allow a response code of 0. I have seen the many
times with PHP/cURL, as it uses HTTP 0 to indicate a timeout. Can you
attempt posting a failing status via curl on the command line and see
if that works? That should at least rule out any network issues.
that a bit the past few days as well (it looks like
the email I sent to the list yesterday about curl multi was an HTTP
Status 0 issue).
We were outputting the curl output from our app to a file for a bit -
it definitely seemed like the cases with status code 0 weren't
communicating
the email I sent to the list yesterday about curl multi was an HTTP
Status 0 issue).
We were outputting the curl output from our app to a file for a bit -
it definitely seemed like the cases with status code 0 weren't
communicating with Twitter - I've pasted some sample output at the end
of the email
I've been seeing the same thing - it started about 3 days ago. I
installed a qd delay/retry loop to manage it and log the times on a
couple of API calls - rate_limit_status.json test.json
It seems to be mostly gone today - has only happened once so far at
07:02:22.
Yesterday this was a
The times may help me do some network troubleshooting, what timezone
is that?
On Feb 20, 2009, at 08:13 AM, swggy wrote:
I've been seeing the same thing - it started about 3 days ago. I
installed a qd delay/retry loop to manage it and log the times on a
couple of API calls -
Steve's comment that he's seen this over the past few days over set
timespans - in our case, the problems are most prevalent between noon
and 6PM, eastern.
Also, here's my full traceroute:
Packets
Pings
Host
Howdy,
I am making API calls to Twitter using PHP ('Arc90 Twitter API Client'
Library) to update a users status, and about 3 out of 10 times CURL
returns a HTTP status code of 0 - with no other data returned.
But if I try again and again it will usually work within a few
repeats. Does anyone
