Can you guys consider adding the feature to Cache Everything by means of using Headers without the use of Page Rules? It will be easy to manage and could really help in caching more pages and reducing the origin hits.
Something like:
header('CF-Cache: CacheEverything, EdgeCacheTTL=2HRS');
It’s more or less transparent as to whether CF is hitting the browser or the cache at the other end. If you use CacheEverything and then set the correct Cache-Control/Expires headers at your server, you’ll get the outcome you want.
For example, send these headers from your origin to not cache a resource:
Cache-Control: no-cache
To cache for 1 hour, but the client should still hit CF (and sometimes origin) to check for update:
Cache-Control: public, max-age=3600
To cache a resource for 1 year and CF/the browser shouldn’t try and poll to see if it was updated:
Cache-Control: public, max-age=31536000, immutable
Just make sure not to set a browser or origin cache TTL override.
So even using with must-revalidate
header('Cache-Control: public, max-age=3600,must-revalidate');
the client may HIT Cloudflare sometimes (also sometimes origin)?
According to this page:
https://support.cloudflare.com/hc/en-us/articles/115003206852-Understanding-Origin-Cache-Control ,
must-revalidate will re-validate at Cloudflare but not necessarily at the browser, so it seems like it would hit the origin. Be careful because no browser invocation means no Cloudflare invocation.
I’m not sure whether a successful re-validation (origin responds content not changed) would read as HIT. I would think so.
It should be REVALIDATED.