add(considered): Cache-Status is standardised but not the default anywhere - #171
Draft
jdevalk wants to merge 1 commit into
Draft
add(considered): Cache-Status is standardised but not the default anywhere#171jdevalk wants to merge 1 commit into
jdevalk wants to merge 1 commit into
Conversation
…where RFC 9211 gives every cache on the path one vocabulary for hit/miss/ttl, replacing CF-Cache-Status, X-Cache and friends. It has been Standards Track since June 2022 and its authors work at Cloudflare, Akamai and Fastly — but Nottingham's August 2026 survey of 120M responses found ~1.1M Cache-Status instances against tens of millions of proprietary equivalents. Squid and Caddy ship it; Cloudflare and nginx do not. Recommending it today would have readers hand-configure a header their CDN does not emit, alongside the proprietary one it does. Turned down on adoption grounds per the routine; recorded rather than dropped. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
9e809ae
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b16cf352.specification-website.pages.dev |
| Branch Preview URL: | https://add-considered-cache-status.specification-website.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Adds one entry to
src/content/considered/—cache-status.md, filedtoo-early. No spec page, no changelog entry (a/considered/entry is not spec content).Why now
Mark Nottingham published Informing HTTP Extension Design with Data on 7 August 2026 — a
cc-lintsurvey of 120 million responses across ~50,000 sites in the Tranco top 100,000. The daily scan already mined it for theX-XSS-Protectionfigure; the un-mined finding is the cache-header gap:Cache-Status(RFC 9211): ~1.1 million instancesX-Cache,CF-Cache-Status, …): tens of millionsProxy-Status(RFC 9209): ~7,900 instancesSo the standardised header exists, is finished, and is losing to the incumbents by roughly thirtyfold.
Primary sources
Why turned down rather than specced
Two reasons, both in the entry:
CF-Cache-Statusand nginx has no native path. A reader following our advice would hand-configure a header their CDN does not produce.optional, so the shape is not disqualifying — but Server-Timing has no incumbent and this does.revisit: a default-on implementation at a CDN with real market share (Cloudflare emittingCache-Status, or Fastly without a VCL recipe); nginx shipping it would count too.Open question for the maintainer
This is a thin-adoption call, which per
ops/routines/daily-standards-scan.mdis yours, not the scan's. If you read ~1.1M instances plus Squid/Caddy as enough adoption, say so and I'll write the page instead and drop this entry in the same PR.Checks
npm run build,npm run lint,npm run format:checkandnpm run check:skillall pass. Entry renders at/considered/.🤖 Generated with Claude Code