Cloudflare Pages Cache / and cache warm-up
The Essence of My Problem
I have a website (built with Astro.js + WordPress) on a domain, and I’ve set up caching rules (Cache Everything). In the middleware function, I added the following logic to cache HTML pages, as they are not cached by default:
newHeaders.set(
"Cache-Control",
"public, max-age=0, must-revalidate, s-maxage=31536000, stale-while-revalidate=86400"
);
I don’t understand how I can warm up the cache (ideally for all visitors and globally across the world) so that each page is pre-warmed for every individual user.11 Replies
Pages does its own caching, which can break if you try to add caching yourself. Just adding the header should be fine though
"Caching yourself" you mean my caching rules "Cache Everything" ?
By "header," do you mean the newHeaders.set in my middleware function?
By "header," do you mean the newHeaders.set in my middleware function?
1. Yes, that or using the Cache API within your Middleware
2. Yes, setting a Cache-Control header on its own shouldn't do anything. If an object is eligible for cache, it will be cached. If it isn't, it wouldn't be
Okay, thank you, I'll try to test it only with
newHeaders and without Cache Rules.
If you don’t mind, can I ask you a few more questions on this subject ? because I’ve been suffering for two weeks with these questions :NotLikeThis:
1. Is there a way to pre-warm the cache for all pages on Cloudflare Pages globally across all regions?
2. Can Cache Reserve help with global cache warming?
3. What’s the best way to simulate requests from multiple regions to warm the cache?
4. Does Tiered Cache or Smart Tiered Caching Topology help with cache warming?
Thank you in advance :MeowHeartCloudflare:1. Not really, or not without extreme cost. Pages' "regions" is every datacenter that Cloudflare operates out of(which is a quite substantial number).
2. No, it just adds another layer to the cache, it doesn't do any warming.
3. A tool like https://globalping.io/ might help, but only if users are hitting the exact datacenter that globalping hits.
4. No, since Pages backing store(which is what performs the caching) does not interact with Tiered Caching.
I would deploy your project, and then see what performance looks like, before building a complex setup to warm caches. In most cases, base performance on Pages should be more than enough
Globalping
Globalping - Internet and web infrastructure monitoring and benchma...
Run free latency tests and network commands like ping, traceroute, HTTP and DNS resolve on probes located worldwide.
Oh, even so 😢
Btw, I've deployed my project already. Should I provide you a link ?
Or should I cancel the caching rules first?
Maybe test it out with/without the Cache Rules? It shouldn't make much of a difference performance-wise, but if it does provide a boost, then you would know for yourself
Yes, as I can see, once I disabled the Caching Rules, my pages stopped being cached, and every time I revisit a page, it reloads again.
Here are the options I have in Cache Rules:
- All incoming requests
- Eligible for cache
- Use cache-control header if present, bypass cache if not
What you really want is caching in the browser, where it is most effective. You shouldn't need to care about caching within Pages itself
I won’t have any trouble cleaning this cache (in the browser) for the whole site or a specific page?
Your cache headers explicitly tell the browser to not cache at all, but revalidate on every request. You could probably increase that a little bit
I would only put cache headers on immutable assets though
And let Pages handle headers for the other assets