Security Rate limiting Rule seemingly over-applying incorrectly
We have a security rule in place that will match the following
I cannot see in the analytics anyone who has anywhere near this amount of requests. This has caused our service to be unsuable by many customers in multiple situations.
- Hostname : our hostname
- Custom counting expression
- Response statuscode equals 404
(http.response.code eq 404)
- Response statuscode equals 404
- when rate exceeds: 3000 per 1 minute
- Take action: Block with default rate limiting response and status 429 for 1hr
I cannot see in the analytics anyone who has anywhere near this amount of requests. This has caused our service to be unsuable by many customers in multiple situations.
