W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2010

API Rate Limits and HTTP Code

From: Karl Dubost <karl+w3c@la-grange.net>
Date: Thu, 28 Oct 2010 16:50:43 -0400
Message-Id: <827182B5-E3B3-4762-AF6A-D34B8EB4B72E@la-grange.net>
To: HTTP Working Group <ietf-http-wg@w3.org>

I have seen a few times blog post (example [1]) over API Rate Limits and HTTP response code. People designing APIs have difficulties it seems to find the appropriate HTTP response code. That led me a few weeks ago to look at what was done at a few services (not a complete survey, just curiosity)

There is no common practice around that. Should the HTTP specification have a specific code for this, or is there already everything appropriate?

[1]: http://mehack.com/inventing-a-http-response-code-aka-seriously
[2]: http://lists.w3.org/Archives/Public/www-archive/2010Oct/0000
[3]: http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-12#section-8.4

Karl Dubost
Montréal, QC, Canada
Received on Thursday, 28 October 2010 20:51:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:55 UTC