3 ms·
> {"error":"Too many requests, please try again later."} I guess it still works.
by varun_ch 1y ago
> {"error":"Too many requests, please try again later."}
I guess it still works.
- lgl 1y agoBug report: when the server is overloaded, the No's are no longer random :)
- kenrick95 1y agoClassic Hacker News hug of death
- xnorswap 1y agoIt looks like it's limited to 10 requests per minute, it's less of a hug and more of a gentle brush past. It's documented as "Per IP", but I'm willing to bet either that documentation is wrong, or it's picking up the IP address of the reverse proxy or whatever else is in-front of the application server, rather than the originator IP. Why do I think that? Well these headers: x-powered-by Express x-ratelimit-limit 10 x-ratelimit-remaining 0 Which means it's not being rate-limited by cloudflare, it's express doing the rate limiting. And I haven't yet made 10 requests, so unless it's very bad at picking up my IP, it's picking up the cloudflare IP instead.
- NotMichaelBay 1y agoIt's so elegant. Even in failure, it's still operational.
- riquito 1y agoLove it, it's brilliant, but I think the rate limiting logic is not doing what the author really wants, it actually costs more cpu to detect and produce the error than returning the regular response (then my mind goes on how to actually over optimize this thing, but that's another story :-D )
- hotheadhacker 1y agoRate limiting has been removed