Sure @fritex, I’m using Jmeter to do the concurrence tests and, I’m testing my website which has Cloudflare configured as a Middleware, which is why I get the specific 429 error from Cloudflare.
Here you can find a snippet of one of the error codes:
Thread Name:Concurrencia Test-ThreadStarter 1-260
Sample Start:2022-10-31 11:08:28 WET
Size in bytes:531
Headers size in bytes:531
Body size in bytes:0
Data type ("text"|"bin"|""):
The ResponseData is empty and, the response headers are:
Date: Mon, 31 Oct 2022 11:10:08 GMT
Cache-Control: no-store, no-cache
I do not have any Rate Limiting Rules and, I don’t see any documented ones regarding the tests that I’m doing. And in the case that I’ve getting blocked by any of these, I would be getting a
Retry-After header as I see in the
Configuring-Cloudflare-Rate-Limiting document, which I’m not.
@eva2000 Are there any ways of telling if I’m getting blocked by this limiting?
As my test descends into doom (starts with one error, then 3, then 15, then all the requests are error), my server through Cloudflare is unavailable. But I do not get this behaviour when testing directly as I get all successful requests.
Even when I do the test through Cloudflare and I get a lot of errors, I can see that after some time, my server did responded all of the requests, so they are all marked with a