3 ms·
Arguably that should be a 5xx response though; there's nothing wrong with the requests, the server just doesn't want to (doesn't have enough resources to) handl
by a1369209993 6y ago
Arguably that should be a 5xx response though; there's nothing wrong with the requests, the server just doesn't want to (doesn't have enough resources to) handle them as quickly as they're being issued.
- another-dave 6y agoI guess breaking the rate limit is a user error — e.g. sometimes if you continue with could get your access revoked. I read 50x as "something not your fault" went wrong.
- masklinn 6y agoYup. 500 errors are "the server is broken" (aka the server fails to fulfil the request), 400 errors are "the client did something it should not", including every case of "the client did something the server took issue with for whatever reason". In fact RFC 6585 added "429 Too Many Requests" specifically for rate-limiting scenarios. 413 (payload too large), 414 (URI too long) or 431 (header fields too large) are likewise things which may technically be valid according to the HTTP spec in general, but which the server rejects.