토론: Cache-Control directives: max-age, no-store, private and stale-while-revalidate

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

번역이 없어 원문을 표시합니다. 원문

'HTML and API responses that change: `no-cache` plus an `ETag`' is safe for public content and unsafe for anything personalised, and the bullet for per-user responses does not close the gap. `no-cache` permits a shared cache to store the response and serve it after revalidation; RFC 9111 keeps responses to requests with an `Authorization` header out of shared caches unless `public`, `s-maxage` or `must-revalidate` says otherwise, but a cookie-authenticated response has no such protection. The failure then runs as follows: the cache stores user A's page under the URL, user B requests it, the cache revalidates with A's `ETag`, the origin compares only the tag and answers 304, and the cache serves A's body to B. Personalised responses therefore need `private` (or `no-store`) regardless of `no-cache`, and an origin that answers conditional requests must make its 304 decision depend on the principal, not only on the resource. `Vary: Cookie` is the weaker fallback, since it fragments the cache per cookie value and still trusts the origin's 304. I would rewrite the bullet as 'public content that changes: `no-cache` plus `ETag`; anything that depends on who asks: `private, no-cache` plus an `ETag` the origin checks per user'.

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

번역이 없어 원문을 표시합니다. 원문

Three additions from the same family of specifications. RFC 9213 (Targeted HTTP Cache Control) defines `CDN-Cache-Control` and the pattern for provider-specific fields such as `Cloudflare-CDN-Cache-Control`: a CDN that implements it obeys the targeted field instead of `Cache-Control`, so an origin can keep a long lifetime at the edge and a short one in browsers without `s-maxage` contortions. RFC 9111 also defines `must-understand`, meant to be paired with `no-store`: a cache that understands the response's status code may store it despite `no-store`, one that does not must not, which is how responses with new status codes are made safe to cache. On precedence: when `max-age` (or `s-maxage` for a shared cache) is present, a cache must ignore `Expires`, so a stale `Expires` left by a framework does no harm once `Cache-Control` is set, whereas a response with only an `Expires` in the past is already expired rather than 'without directives'. And since `max-age` counts against `Age`, each cache in a chain adds its residency time, so a browser behind a CDN sees slightly less than the advertised lifetime.