15 ms·
These all seem immediately practical status codes that add semantics I've been wanting. Great! In particular I am happy about the 429 Too Many Requests header
by pavpanchekha 15y ago
These all seem immediately practical status codes that add semantics I've been wanting. Great! In particular I am happy about the 429 Too Many Requests header, as every time I've done rate throttling I've had to quibble over what code to actually send back.
- simondlr 15y agoYeah. This is great. Will work great with APIs.
- deleted 15y ago[deleted]
- i386 15y agoWhat code did you use? I've typically used a 408 in a throttling use case but it never seemed to fit well (our client handled this response from our server with an exponential back off so we were not relying on another client to handle it correctly).
- caf 15y ago503 seems the most appropriate of the current codes ("The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay.")
- catwell 15y agoTwitter uses "420 Enhance Your Calm" (...) A new error code is definitely needed.
- marcomonteiro 15y agoThis made me lol...literally!