fix(server): force stylesheet revalidation with no-cache + content ETag #19
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/style-cache-headers"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
/style.cssnow sendsCache-Control: no-cacheplus a content-hashETag(first 16 hex of sha256), asserted inTestStyleSheetServesWithCorrectType.Why
Proxies/tunnels (e.g. Cloudflare) were serving stale dock CSS after deploys — the handler previously sent no cache directives, so old layouts survived restarts. no-cache forces revalidation on every load; the ETag keeps unchanged reloads cheap.