Re: [twitter-dev] Re: Rate limit HTTP response

2010-01-29 Thread Abraham Williams
An HTTP code of 0 is fairly common with cURL if it can not connect. It could be related to randomly dropped connections by your network hardware or further out. Abraham On Thu, Jan 28, 2010 at 11:33, John Kalucki j...@twitter.com wrote: Is the HTTP code really 0, or did you receive a TCP reset

[twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread Richard
We see quite a few TweetDeck users complaining of mysterious 0 API limits here. No other apps in use and very few API calls made, suddenly down to 0. Looks to be some kind of API issue here... On Jan 27, 11:59 pm, EastSideDev eastside...@gmail.com wrote: Prior to doing a rate-limit API, I always

[twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread EastSideDev
Perhaps we can get someone from Twitter to comment on it. The issue is not 0 API limits, it's an HTTP code 0. On Jan 28, 4:02 am, Richard richardbar...@gmail.com wrote: We see quite a few TweetDeck users complaining of mysterious 0 API limits here. No other apps in use and very few API calls

Re: [twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread John Kalucki
Is the HTTP code really 0, or did you receive a TCP reset without any bytes read and your HTTP library is returning a code of 0? (There may be other error indication flags in the client which aren't being checked before testing the HTTP response code.) Or, perhaps the the HTTP response header

[twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread Rich
We are seeing this too in the HTTP headers, basically our app is useless right now as it's returning invalid rate limit information On Jan 28, 7:33 pm, John Kalucki j...@twitter.com wrote: Is the HTTP code really 0, or did you receive a TCP reset without any bytes read and your HTTP library is

Re: [twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread Will Fleming
I am currently getting a HTTP 400 response when interacting with the API, with a error message of Rate limit exceeded. Clients may not make more than 0 requests per hour. OAuth for authentication. No calls currently working, but same result on both

Re: [twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread Will Fleming
One other thing, API calls to http://search.twitter.com do appear to be working correctly.

[twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread Shelkie
Are others having trouble with Ratelimits? Suddenly the X-Ratelimit-Limit has changed to 0 for several accounts I have checked. Here are some sample HTTP headers: [Date] = Thu, 28 Jan 2010 21:27:55 GMT [Server] = hi [X-Ratelimit-Limit] = 0 [Status] = 400 Bad Request [X-Ratelimit-Remaining]

[twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread Rich
Looks like they are in the process of upping the oAuth rate limit as now I'm getting different results but still a 400 error On Jan 28, 9:41 pm, Shelkie eshel...@gmail.com wrote: Are others having trouble with Ratelimits? Suddenly the X-Ratelimit-Limit has changed to 0 for several accounts I

[twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread Rich
Just run it through my debugger, it's absolutely returning an HTTP 400 response On Jan 28, 9:46 pm, Rich rhyl...@gmail.com wrote: Looks like they are in the process of upping the oAuth rate limit as now I'm getting different results but still a 400 error On Jan 28, 9:41 pm, Shelkie

[twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread Rich
Interesting my whitelisted account is still working, but the non whitelisted ones are broken over oAuth On Jan 28, 9:48 pm, Rich rhyl...@gmail.com wrote: Just run it through my debugger, it's absolutely returning an HTTP 400 response On Jan 28, 9:46 pm, Rich rhyl...@gmail.com wrote:

Re: [twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread Michael Steuer
We see this too now on a bunch of our test accounts.. Does Twitter have a resolution time? It's making the use and development efforts of our application all but impossible... On Jan 28, 2010, at 1:51 PM, Rich wrote: Interesting my whitelisted account is still working, but the non

Re: [twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread Anton Krasovsky
Happens to me too, a lot of (all?) user accounts are getting Rate limit exceeded. Clients may not make more than 0 requests per hour. error messages. Anton On Thu, Jan 28, 2010 at 9:51 PM, Rich rhyl...@gmail.com wrote: Interesting my whitelisted account is still working, but the non

[twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread morgan
I'm having the same problems. oauth calls from my application are failing with the '0 reqs per hour' message, on both my internal machines and my host at the data center. However, my personal account still flies okay on seesmic etc... It's weird. My app isn't considered aggressive at this point

[twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread Proxdeveloper
I'm getting this error messages while requesting the statuses and DirectMessages from the API. HTTP 400 Error. Is Twitter working on this issue ? On Jan 28, 3:27 pm, Michael Steuer mste...@gmail.com wrote: We see this too now on a bunch of our test accounts.. Does Twitter have a resolution

Re: [twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread Anton Krasovsky
It looks like this problem is affecting api.twitter.com only. I've moved from to twitter.com and it's gone. Anton On Thu, Jan 28, 2010 at 10:04 PM, Anton Krasovsky anton.krasov...@gmail.com wrote: Happens to me too, a lot of (all?) user accounts are getting Rate limit exceeded. Clients may not

Re: [twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread Will Fleming
Requests here seem to be working correctly again, thanks.

Re: [twitter-dev] Re: Rate limit HTTP response

2010-01-28 Thread Xavier Grosjean
Now the problem is different. The headers in the timeline request response headers have a limit set to 350, while the response to the get_rate_limit request still says 150... 2010/1/28 Michael Steuer mste...@gmail.com We see this too now on a bunch of our test accounts.. Does Twitter have a