Hi everyone, hope you’re doing well.
I’ve been experimenting with caddy for serving static sites and noticed something odd, certain assets, especially JS and CSS files, sometimes don’t update immediately after deployment, even with cache control headers in place. This reminds me of conversations I’ve seen about static content loading quirks — almost like how browser games refresh cached assets unpredictably, for example with spell challenges and cache refresh issues on.
So I’m wondering, when caddy appears to serve stale assets even though cache headers are set correctly, do people usually look first at header misconfiguration, browser cache policies, or how intermediary CDNs are handling freshness? And has anyone seen this behavior with dynamic resources too — like WebAssembly modules or service-worker-controlled files?
Thanks in advance — any insight or debugging tips would be really helpful!