1) Looks like the docs got updated.
2) 400 will eventually just be for API calls that are malformed:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1
Abraham
On Sat, Jan 23, 2010 at 18:40, Andy Freeman ana...@earthlink.net wrote:
(1) When will
(1) When will http://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors
be updated?
(2) How does 420 differ from 400?
On Dec 22 2009, 4:19 pm, Wilhelm Bierbaum wilh...@twitter.com wrote:
Eventually the REST API will return the same 420 response code to
indicate rate limiting. We wanted to
i am getting this response code in my twitter search application, how
to resolve the error ?
On Dec 23 2009, 3:44 am, Wilhelm Bierbaum wilh...@twitter.com wrote:
We're changing the response code sent back by the Search API when the
rate limit has been exceeded. At present, it is impossible to
OK ... next question ... are the rate limit HTTP headers from the REST
API now ported to Search and working / documented?
2. HTTP response headers included in all REST API responses which
count against the rate limit:
* X-RateLimit-Limit the current limit in effect
*
Will you be changing the REST API error code to match the Search API?
RE: 420 = rate limit exceeded.
On Dec 22, 4:44 pm, Wilhelm Bierbaum wilh...@twitter.com wrote:
We're changing the response code sent back by the Search API when the
rate limit has been exceeded. At present, it is impossible
yeah, doesn't make much sense to have two different codes indicating that
the limit is exceeded...
2009/12/23 DustyReagan dustyrea...@gmail.com
Will you be changing the REST API error code to match the Search API?
RE: 420 = rate limit exceeded.
On Dec 22, 4:44 pm, Wilhelm Bierbaum
Eventually the REST API will return the same 420 response code to
indicate rate limiting. We wanted to change as little as possible to
get people comfortable with the new response code.
On Dec 22, 4:07 pm, Marco Kaiser kaiser.ma...@gmail.com wrote:
yeah, doesn't make much sense to have two
