Caching won't work

[erictung]

Kindly read this, could be related:

Cache in front of Worker

Currently, no matter what, a Cloudflare Worker will run in front of CF’s cache. This makes Workers unappealing for doing things like serving static content (obtained via a complicated scheme only Workers can do) since you will be billed for every request; in this situation, it makes much more sense to build on another Serverless platform like Lambda or Cloud Functions since then you could have it serve the static content and get CF to cache the responses, all at a fraction of the price of what i…

Cache in front of Worker

So, I think this thread is conflating technical architecture with pricing… A Worker can use the Cache API to implement arbitrary caching logic. A Worker that makes good use of the Cache API should be able to achieve the same performance as if the cache ran in front of the Worker. Hence, there is not a technical reason for Workers to run behind cache. But it sounds like the motivation here is to avoid being billed for requests that hit cache. This assumes that if cache ran in front of Workers, …