For Workers & Pages, what is the name of the domain?
What is the issue or error you’re encountering
Wondering how to avoid using workers
What steps have you taken to resolve the issue?
After discovering that the results of workers could not be cached before hitting the worker (see Cache in front of Worker), I started looking at alternatives.
What I want to be able to do is to have something that’s almost exactly like Pages, but I can, via an API, update single resources/pages. I can think of two options:
-
The obvious is pages + workers, but workers have a 100k/day limit (might be ok), and 1000/min burst limit (which might not be). I naively tried putting my worker endpoint behind a cloudflare proxy, only to waste time and find out that’s not possible (though I wish the documentation made that clear)
-
Host something like a worker on another provider, and then I can, ironically, put that behind the Cloudflare DNS proxy.
I then thought of a third option:
Can a public R2 bucket work seamlessly behind Cloudflare DNS orange/proxy? If that’s the case, I can have a worker (or external service) make an API call to update a single R2 object and purge it from the cache.