4 ms·
hugged to death? anyway - i got a great 429 back with a suggested try-after -time. it made me smile in appreciation! well done!
by TomasEkeli 2y ago
hugged to death?
anyway - i got a great 429 back with a suggested try-after -time. it made me smile in appreciation!
well done!
- theginger 2y agoThat's the wrong status code The HTTP 429 Too Many Requests response status code indicates the user has sent too many requests in a given amount of time ("rate limiting"). Unless the server believes you as an individual user were sending too many it should not have been a 429 If the server was unable to handle the volume of requests more generally it should have been a 503 which also supports Retry-After
- aeaa3 2y agoThe 429 response is sent when rate-limiting (based on IP address). Either something is wrong with my rate-limiting code or there are many people behind a single IP address. Anyway the limits are increased now.
- theginger 2y agoPossible your application isn't seeing real ips, maybe is seeing the IP of a load balancer or similar.
- xp84 2y agoMaybe one request is one Too Many at this point. ;) Call it a very dynamic rate limit that autoscales all the way down to zero.
- 1vuio0pswjnm7 2y agoIME, it is relatively common to get this response code incorrectly, i.e., not triggered by rate. IME, it can be triggered by sending one and only one HTTP request to a site one has never visited before. For example, a request sent to a certain IP address with a certain set of HTTP headers and header values using a certain HTTP method and HTTP version. Despite what "Too many requests" suggests, people writing/configuring software are (accidentally) sending this error in response to requests based on quality not quantity. In each case where I have received it, I was able to make the error go away by changing something about the request.