[twitter-dev] Re: HTTP 409 on status update via API
Same here 408 on all OAuth authenticate attempts. Is it safe to assume this is fallout from DDOS? Any official word on we can expect our apps to work again? On Aug 6, 2:30 pm, Matthew F mcf1...@gmail.com wrote: I'm getting 408s trying to authenticate with OAuth On Aug 6, 10:20 pm, John Kalucki jkalu...@gmail.com wrote: This should be fixed for the Streaming API. -John On Aug 6, 1:59 pm, Jennie Lees trin...@gmail.com wrote: Getting the same thing using the track function of the API. On Thu, Aug 6, 2009 at 9:43 PM, briantroy brian.cosin...@gmail.com wrote: Sorry... these are HTTP 408s... On Aug 6, 1:20 pm, briantroy brian.cosin...@gmail.com wrote: This just started today. It was working fine before and early this morning. I'm send in user updates from a widget via API. My server is whitelisted and I've got a registered service. I get a HTTP 409 on every attempt to submit a status. Not sure why... You can try it here:http://briantroy.com/blog/about I know a 409 should mean timed out... but the response comes back in one second (or just really really fast). Any help appreciated... Brian Roy justSignal -- Jennie Lees Founder, Affect Labs jen...@affectlabs.comhttp://twitter.com/jennielees
[twitter-dev] Re: HTTP 409 on status update via API
I've restored all of my services by doing 3 things: 1) Follow redirects (HTTP 302s) 2) Send UserAgent 3) Send Referer On Aug 6, 9:56 pm, cestre...@gmail.com cestre...@gmail.com wrote: Same here 408 on all OAuth authenticate attempts. Is it safe to assume this is fallout from DDOS? Any official word on we can expect our apps to work again? On Aug 6, 2:30 pm, Matthew F mcf1...@gmail.com wrote: I'm getting 408s trying to authenticate with OAuth On Aug 6, 10:20 pm, John Kalucki jkalu...@gmail.com wrote: This should be fixed for the Streaming API. -John On Aug 6, 1:59 pm, Jennie Lees trin...@gmail.com wrote: Getting the same thing using the track function of the API. On Thu, Aug 6, 2009 at 9:43 PM, briantroy brian.cosin...@gmail.com wrote: Sorry... these are HTTP 408s... On Aug 6, 1:20 pm, briantroy brian.cosin...@gmail.com wrote: This just started today. It was working fine before and early this morning. I'm send in user updates from a widget via API. My server is whitelisted and I've got a registered service. I get a HTTP 409 on every attempt to submit a status. Not sure why... You can try it here:http://briantroy.com/blog/about I know a 409 should mean timed out... but the response comes back in one second (or just really really fast). Any help appreciated... Brian Roy justSignal -- Jennie Lees Founder, Affect Labs jen...@affectlabs.comhttp://twitter.com/jennielees
[twitter-dev] Re: HTTP 409 on status update via API
Sorry... these are HTTP 408s... On Aug 6, 1:20 pm, briantroy brian.cosin...@gmail.com wrote: This just started today. It was working fine before and early this morning. I'm send in user updates from a widget via API. My server is whitelisted and I've got a registered service. I get a HTTP 409 on every attempt to submit a status. Not sure why... You can try it here:http://briantroy.com/blog/about I know a 409 should mean timed out... but the response comes back in one second (or just really really fast). Any help appreciated... Brian Roy justSignal
[twitter-dev] Re: HTTP 409 on status update via API
Getting the same thing using the track function of the API. On Thu, Aug 6, 2009 at 9:43 PM, briantroy brian.cosin...@gmail.com wrote: Sorry... these are HTTP 408s... On Aug 6, 1:20 pm, briantroy brian.cosin...@gmail.com wrote: This just started today. It was working fine before and early this morning. I'm send in user updates from a widget via API. My server is whitelisted and I've got a registered service. I get a HTTP 409 on every attempt to submit a status. Not sure why... You can try it here:http://briantroy.com/blog/about I know a 409 should mean timed out... but the response comes back in one second (or just really really fast). Any help appreciated... Brian Roy justSignal -- Jennie Lees Founder, Affect Labs jen...@affectlabs.com http://twitter.com/jennielees
[twitter-dev] Re: HTTP 409 on status update via API
Same here. 408's on all production servers. Tested on dev servers and thats ok. Might be related to accidental bans from the ddos carpet bombing blocks. On Aug 6, 4:20 pm, briantroy brian.cosin...@gmail.com wrote: This just started today. It was working fine before and early this morning. I'm send in user updates from a widget via API. My server is whitelisted and I've got a registered service. I get a HTTP 409 on every attempt to submit a status. Not sure why... You can try it here:http://briantroy.com/blog/about I know a 409 should mean timed out... but the response comes back in one second (or just really really fast). Any help appreciated... Brian Roy justSignal
[twitter-dev] Re: HTTP 409 on status update via API
This should be fixed for the Streaming API. -John On Aug 6, 1:59 pm, Jennie Lees trin...@gmail.com wrote: Getting the same thing using the track function of the API. On Thu, Aug 6, 2009 at 9:43 PM, briantroy brian.cosin...@gmail.com wrote: Sorry... these are HTTP 408s... On Aug 6, 1:20 pm, briantroy brian.cosin...@gmail.com wrote: This just started today. It was working fine before and early this morning. I'm send in user updates from a widget via API. My server is whitelisted and I've got a registered service. I get a HTTP 409 on every attempt to submit a status. Not sure why... You can try it here:http://briantroy.com/blog/about I know a 409 should mean timed out... but the response comes back in one second (or just really really fast). Any help appreciated... Brian Roy justSignal -- Jennie Lees Founder, Affect Labs jen...@affectlabs.comhttp://twitter.com/jennielees
[twitter-dev] Re: HTTP 409 on status update via API
I'm getting 408s trying to authenticate with OAuth On Aug 6, 10:20 pm, John Kalucki jkalu...@gmail.com wrote: This should be fixed for the Streaming API. -John On Aug 6, 1:59 pm, Jennie Lees trin...@gmail.com wrote: Getting the same thing using the track function of the API. On Thu, Aug 6, 2009 at 9:43 PM, briantroy brian.cosin...@gmail.com wrote: Sorry... these are HTTP 408s... On Aug 6, 1:20 pm, briantroy brian.cosin...@gmail.com wrote: This just started today. It was working fine before and early this morning. I'm send in user updates from a widget via API. My server is whitelisted and I've got a registered service. I get a HTTP 409 on every attempt to submit a status. Not sure why... You can try it here:http://briantroy.com/blog/about I know a 409 should mean timed out... but the response comes back in one second (or just really really fast). Any help appreciated... Brian Roy justSignal -- Jennie Lees Founder, Affect Labs jen...@affectlabs.comhttp://twitter.com/jennielees
[twitter-dev] Re: HTTP 409 on status update via API
They went away for a bit... and now not only am I getting 408's on update but validate credentials is failing as well On Aug 6, 2:56 pm, briantroy brian.cosin...@gmail.com wrote: Now twitter search API calls are hanging... just stall until they time out on my side On Aug 6, 2:30 pm, Matthew F mcf1...@gmail.com wrote: I'm getting 408s trying to authenticate with OAuth On Aug 6, 10:20 pm, John Kalucki jkalu...@gmail.com wrote: This should be fixed for the Streaming API. -John On Aug 6, 1:59 pm, Jennie Lees trin...@gmail.com wrote: Getting the same thing using the track function of the API. On Thu, Aug 6, 2009 at 9:43 PM, briantroy brian.cosin...@gmail.com wrote: Sorry... these are HTTP 408s... On Aug 6, 1:20 pm, briantroy brian.cosin...@gmail.com wrote: This just started today. It was working fine before and early this morning. I'm send in user updates from a widget via API. My server is whitelisted and I've got a registered service. I get a HTTP 409 on every attempt to submit a status. Not sure why... You can try it here:http://briantroy.com/blog/about I know a 409 should mean timed out... but the response comes back in one second (or just really really fast). Any help appreciated... Brian Roy justSignal -- Jennie Lees Founder, Affect Labs jen...@affectlabs.comhttp://twitter.com/jennielees
[twitter-dev] Re: HTTP 409 on status update via API
I'm getting the same thing on any type of profile or background image I attempt to update. Any know anything about this?? All I get are 400 or 408's Ugh On Aug 6, 7:24 pm, briantroy brian.cosin...@gmail.com wrote: They went away for a bit... and now not only am I getting 408's on update but validate credentials is failing as well On Aug 6, 2:56 pm, briantroy brian.cosin...@gmail.com wrote: Now twitter search API calls are hanging... just stall until they time out on my side On Aug 6, 2:30 pm, Matthew F mcf1...@gmail.com wrote: I'm getting 408s trying to authenticate with OAuth On Aug 6, 10:20 pm, John Kalucki jkalu...@gmail.com wrote: This should be fixed for the Streaming API. -John On Aug 6, 1:59 pm, Jennie Lees trin...@gmail.com wrote: Getting the same thing using the track function of the API. On Thu, Aug 6, 2009 at 9:43 PM, briantroy brian.cosin...@gmail.com wrote: Sorry... these are HTTP 408s... On Aug 6, 1:20 pm, briantroy brian.cosin...@gmail.com wrote: This just started today. It was working fine before and early this morning. I'm send in user updates from a widget via API. My server is whitelisted and I've got a registered service. I get a HTTP 409 on every attempt to submit a status. Not sure why... You can try it here:http://briantroy.com/blog/about I know a 409 should mean timed out... but the response comes back in one second (or just really really fast). Any help appreciated... Brian Roy justSignal -- Jennie Lees Founder, Affect Labs jen...@affectlabs.comhttp://twitter.com/jennielees