Response
Hi Customer,
Thanks for sharing the curl output — that was very helpful. I noticed your server is returning the following header:
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
This essentially instructs Cloudflare (and browsers) not to cache your content. Since Cloudflare respects your origin server’s cache headers, the resources are being passed through rather than cached.
To fix this, you have a couple of options:
Adjust your origin server’s cache headers so they allow caching.
Or, if you want Cloudflare to cache despite the headers, you can create a Page Rule or Cache Rule in the Cloudflare dashboard that overrides them.
I tested this by re-requesting your site and confirmed that with the current headers, caching is bypassed. Once headers are updated (or a Page Rule is applied), caching should start working as expected.
Happy to help configure the right rule if you’d like!
Best regards,
Thought Process
Cloudflare respects origin headers by default. If an origin explicitly disables caching,
the CDN won’t cache unless instructed to ignore or override via rules.
Tools I Would Use
- curl -I: To inspect HTTP response headers.
- Cloudflare Dashboard (Caching): To apply cache level overrides.
- Cloudflare Analytics: To confirm cache HIT/MISS ratios.