Cloudflare caching ignoring no-store?
I have a pretty simple worker that proxies requests to a CDN with some added goodies. Since the CDN is pretty slow, it's nice to have Cloudflare caching the response of the worker, too. But when I added a
?reload search parameter which should force the worker to refetch from the CDN, it still seems to be caching the response. I made it by setting the Cache-Control header to no-store (as opposed to the default public, max-age=3600), which should, AFAIK, bypass the Cloudflare cache. However, when I look at the responses from my worker, I'm still seeing Cf-Cache-Status: HIT. Am I doing something wrong?1 Reply
The response from the Worker isn’t cached by CF unless you’re doing it in the Worker with the Cache API
If you’re adding no-store in your Worker, it has no impact on the asset already cached by fetch()