Loading…
8
Turns out my 2019 rate limit config was the thing saving us from a bot flood
We had a client in Austin get hammered last month and I figured we'd need a full WAF overhaul, but digging in showed the old threshold we set years ago was doing all the heavy lifting, so has anyone else found their legacy API rules were secretly the right call?
1 comments
Log in to join the discussion
Log In1 Comment
caleb_stone19d ago
Did the bot flood actually slow down before you checked the logs, or was the rate limit just masking a bigger problem that's been building quietly this whole time?
-1