content(performance): add Compression Dictionary Transport (RFC 9842)#29
Merged
Conversation
- open-graph: drop dead MDN "Open Graph protocol" page (Web/OpenGraph now 404s; MDN removed the standalone page). Primary source ogp.me already cited, so coverage is unaffected. - hreflang: Google renamed the docs path segment specialized -> specialty; old URL 404s. - global-privacy-control: GPC spec moved to the W3C org (w3c.github.io/gpc/); old globalprivacycontrol.github.io/gpc-spec/ 404s. Bumped `updated` on each. URLs verified live before committing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
New page documenting RFC 9842 (Standards Track, Sept 2025): using a prior response or dedicated dictionary as a Brotli/Zstandard dictionary (dcb/dcz content codings, Use-As-Dictionary / Available-Dictionary headers). Wired into relatedSlugs on compression, cache-control, and http3. Status: optional — a published standard that degrades gracefully, but single-engine browser support today and requires deliberate server/CDN dictionary configuration, so not yet recommended for every site. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
cf6e413
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://dc5d6d1e.specification-website.pages.dev |
| Branch Preview URL: | https://content-compression-dictiona.specification-website.pages.dev |
…ictionary-transport # Conflicts: # src/content/spec/performance/cache-control.md # src/content/spec/performance/compression.md
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
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
New spec page: Compression Dictionary Transport under
performance/, plusrelatedSlugswiring oncompression,cache-control, andhttp3.Why now
RFC 9842 — Compression Dictionary Transport — was published Standards Track in September 2025. It registers two new HTTP content codings (
dcbDictionary-Compressed Brotli,dczDictionary-Compressed Zstandard), theUse-As-Dictionary/Available-Dictionary/Dictionary-IDheader fields, and thecompression-dictionarylink relation — all now permanent in the IANA registries. It's a real, finished standard that sits one layer above our existingcompressionpage, and our daily standards scan flagged it as the strongest uncovered topic.Primary source(s)
Status & justification
optional. It's a published standard and pure progressive enhancement (clients that don't sendAvailable-Dictionaryjust get a normalbr/gzipresponse — nothing breaks). But browser support is still Chromium-led and it requires deliberate server/CDN dictionary management, so it doesn't meet the bar forrecommended("a modern site should do it") yet — it's an advanced, context-dependent optimisation. Per the status discipline,requiredis reserved for "the platform breaks without it", which is not the case here.Notes
npm run buildpasses (135 pages indexed).🤖 Generated with Claude Code