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.
Thanks;
– Matt Sanford / @mzsanford
Twitter API Developer
On Apr 24, 2009, at 05:09 AM, Chris wrote:
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 reverted back from using OAuth a few days ago (to classic HTTP
Auth), and it seems to be since then. Curiously enough it worked fine
about a month ago before I implemented OAuth,
Thanks for your help,
Chris.
