5 ms·
you have to be extremely careful with setting headers for objects or every request will be proxying for an image from Cloudflare, back to the internet,
by cbr 14y ago
you have to be extremely careful with setting headers
for objects or every request will be proxying for an
image from Cloudflare, back to the internet, then to
your servers, then back through the internet, through
Cloudflare and then finally to the user.
I'm pretty sure PageSpeed Service will do this too if you set headers to prohibit caching (which is depressingly common).
- druiid 14y agoI imagine that would be correct, yeah. If you don't specify to cache something, it shouldn't be cached. If a proxy out there still caches it, I'd consider it broken.
- cbr 14y agoFrom memory, if something has no caching headers PageSpeed Service will treat it as Cache-Control: public, max-age=600 Combined with serving html as uncacheable, this is a pragmatic and functional way of dealing with the many sites that haven't put much (any) thought into caching.
- xpose2000 14y agoI just looked at the PageSpeed dash, if no cache headers are specified then it defaults to 1800 seconds.
- druiid 14y agoAh, interesting. Thanks for noting this. Something I'll keep in mind if we ever look at the PageSpeed service. I'm actually not certain if Cloudflare is doing something similar for pages with no headers set.