- From: Karl Dubost <karld@opera.com>
- Date: Sat, 29 Jan 2011 08:41:52 -0500
- To: Mark Nottingham <mnot@mnot.net>
- Cc: Bryce Nesbitt <bnesbitt@bepress.com>, HTTP Working Group <ietf-http-wg@w3.org>
Le 29 janv. 2011 à 00:04, Mark Nottingham a écrit : > It seems like you want the scope of the 503 on the Retry-After to be the entire server, correct? I.e., on a 200, its semantic is roughly "here's your answer, but don't ask me (the server) another question for n seconds." Given the example below I would say for a group of URIs pattern more than the full server. you could set for sure api.example.com but if the server is done with a example.com/api example.com/profile or even example.com/api2 And there are different limits based on your subscription levels: Premium for api and silver for api2. Le 28 janv. 2011 à 14:19, Bryce Nesbitt a écrit : > I'm talking about incremental retrieval of a large data set. Each > resource is new to the client, and will not be cacheable: > > GET /oai2.cgi?token=Az123Z&offset=0&count=100&query='Obama' > HTTP/1.1 200 > Retry-After: 10 > Cache-Control: no-store, no-cache, private > > GET /oai2.cgi?token=Az123Z&offset=100&count=100 > HTTP/1.1 503 Excessive queries from this IP address. Please respect > the Retry-After header. > Retry-After: 10 > Cache-Control: no-store, no-cache, private -- Karl Dubost - http://dev.opera.com/ Developer Relations & Tools, Opera Software
Received on Saturday, 29 January 2011 13:42:34 UTC