we are currently developing a part of our api with the help of Cloudflare Workers (which I think are a great feature by the way). If we test this api with our unit tests, we get back errors after about 100 requests to our api.
Also strange is, that we get a 429 status from Cloudflare for some routes of the api (those routes which end in a fetch to one of our file backends), but a 404 status for some other routes which solely run in the Cloudflare worker.
If we wait a few minutes the tests which failed before run now without a problem, so this couldn’t be a bug in the api or tests.
We do not have activated the Rate Limiting feature under Firewall, so we wonder if there is some internal rate limiting for workers.
The documentation says:
Cloudflare does impose a number of abuse protection methods which are designed not to affect well-intentioned traffic. If you send many thousands of requests per second from a small number of client IP addresses, you can inadvertently trigger some of the protection methods. If you receive 1015 errors in response to traffic you believe should be allowed, please contact us to have the limits adjusted.
But we’re clearly don’t have thousands of requests per second with our tests (rather 100 per minute) and we also don’t get 1015 errors.
Does anyone know about such limitations or can help us with some information, because in production there will certainly be a little more then 100 request for one client (and therefore one ip) per minute?
Thank you in advance