Finally :)

Time to migrate rarely-updating websites that still need a CMS to Cloudflare.

> One thing to watch: when caching is enabled, requests that are normally free — static asset requests and worker-to-worker invocations through service bindings or ctx.exports — are billed at the standard request rate, because each one now consults the cache in front of your Worker.

That’s a very weird limitation from a product standpoint. You might end up spending more money by enabling caching.

I wonder if static assets and worker-to-worker invocations are really more expensive to them with caching enabled, or if this is just a metering problem.

I would have made this free in the interest of making billing simpler and of making the decision to enable caching more straightforward.

If you’re min-maxing costs, this encourages awkward setups where you split workers into two, one with caching enabled and one with caching disabled.