Ratelimiting : additional bypass rule




It would really be nice if the rate limiting bypass rule could be extended to white-list an IP address, a user-agent or using any other http header.
I do see the potential of rate limiting, but currently, when running performance tests, stress tests, or when starting our internal content crawler, rate limiting rule will always kick-in and block the traffic, we should be able to bypass rate limiting for some well-known devices.
Any workaround is more than welcome, rate limiting is a must, and currently I can’t us it as much as I should.

Best regards,