hugged to death?
anyway - i got a great 429 back with a suggested try-after -time. it made me smile in appreciation!
well done!
anyway - i got a great 429 back with a suggested try-after -time. it made me smile in appreciation!
well done!
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
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.
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.
Call it a very dynamic rate limit that autoscales all the way down to zero.