I’m using a reverse proxy in front of workers in order to optimize China user experence.
But during I’m ApacheBench-ing my reverse proxy, I got a 429 response.
As far as I know, this is a pretty common issue
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…
Workers (bundled) hosted at ente.workers.dev are throwing 429 to well-intentioned clients.
I had previously raised a support ticket regarding this and the support executive had removed all zone+ip sub-request limit from the workers, resolving the issue:
But the issue has now reappeared, leading to a production outage.
I can see under Firewall → Activity Log that these events have worker as the rule ID.
I raised a ticket with Cloudflar…
Ah, logflare is from you
I checked out the logflare worker source but by that time we already implemented our own very similar request logging (Catching responses > Pushing straight to Google Pubsub > Big Query > Datastudio).
As a workaround I would assume you want to fallback to collecting stats in buckets and emitting them in intervals when high load is detected?
@harris thanks so much for your kind words Our whole office was celebrating the launch of o…
which could be solve by ask support.
So I make a post to try if we could disable those limit.
Here is my ticket