New Rate Limiting Feature Broken?
Figured I'd move the discussion from workers-and-pages-discussions to here.
Hey all,
We are testing out the beta rate limiting feature for Cloudflare workers and it appears that it is somewhat broken. I understand that this is eventually consistent, but it appears that this consistency is never achieved.
For the sake of testing, I have set the threshold very low - 1 within 60 seconds.
I then run a tool which sends HTTP requests to the endpoint in question and returns whether it was rate limited. I have uploaded the screenshots which shows the result of running each request sequentially. Bearing in mind the requests start at 1:39:21 PM and finishes at 1:39:45 PM which IMO is a substantial amount of time given for things to become "consistent" especially given the limit being "1".
Is there some gotchas I am unaware of? This seems frankly bizarre. The key is based on my IPV6 address and I've ensured that this remains consistent for each request.
Hey all,
We are testing out the beta rate limiting feature for Cloudflare workers and it appears that it is somewhat broken. I understand that this is eventually consistent, but it appears that this consistency is never achieved.
For the sake of testing, I have set the threshold very low - 1 within 60 seconds.
I then run a tool which sends HTTP requests to the endpoint in question and returns whether it was rate limited. I have uploaded the screenshots which shows the result of running each request sequentially. Bearing in mind the requests start at 1:39:21 PM and finishes at 1:39:45 PM which IMO is a substantial amount of time given for things to become "consistent" especially given the limit being "1".
Is there some gotchas I am unaware of? This seems frankly bizarre. The key is based on my IPV6 address and I've ensured that this remains consistent for each request.
