Hi there Steve, As you've noticed, Search API rate limiting is applied and handled quite differently from the rest of the REST API. In the case of Search, when everything is operating under typical conditions, a Retry-After HTTP header will be sent to you (not an X-Retry-Header) -- the value of that header will contain an integer indicating the number of seconds to wait until issuing additional search API requests.
Taylor On Sun, Mar 20, 2011 at 10:43 AM, hax0rsteve <hax0rc...@btinternet.com>wrote: > > > Hi all, > > A question w/r/t HTTP responses when rate limiting is applied, which I'm > hoping > some kind soul will answer before I start hammering away at the API in > careless > experimentation : > > 420 Enhance Your Calm > > I understand from the docs that when this status code is returned, a > "Retry-After" > header will be returned in my http response, does this take the same format > as > the other rate headers e.g. : > > X-RateLimit-Limit: 350 > X-RateLimit-Remaining: 350 > X-RateLimit-Reset: 1277485629 > > so the Retry-After header will be "X-Retry-After:" ? Or is it some other > format ? > > Obviously I could find out by jamming a huge number of search requests at > the API, > but it would be nice to know what to look for beforehand so that I can tell > when to stop :) > > Thank you kindly. > > > hax0rsteve > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk