Implement zstd content-encoding support
Categories
(Core :: Networking: HTTP, enhancement, P2)
Tracking
()
People
(Reporter: jesup, Assigned: jesup)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-complete, Whiteboard: [necko-triaged])
Attachments
(3 files)
Assignee | ||
Comment 1•6 months ago
|
||
Updated•6 months ago
|
Assignee | ||
Updated•4 months ago
|
Updated•3 months ago
|
Assignee | ||
Comment 2•3 months ago
|
||
Assignee | ||
Comment 3•3 months ago
|
||
Pushed by rjesup@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9fb8ccb2f305 Import of zstd library r=sylvestre,necko-reviewers,valentin https://hg.mozilla.org/integration/autoland/rev/dc2ad0369b86 Implement zstd content-encoding support r=necko-reviewers,valentin https://hg.mozilla.org/integration/autoland/rev/94e286542c9d Mark fetch zstd wpt tests as passing r=necko-reviewers,valentin
Comment 5•3 months ago
|
||
Backed out for causing for causing dt failures on browser_net_copy_as_powershell.js
Assignee | ||
Comment 6•3 months ago
|
||
Trivial fix; just needs ", zstd" added to some canned response headers it compares to
Pushed by rjesup@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/68f119112940 Import of zstd library r=sylvestre,necko-reviewers,valentin https://hg.mozilla.org/integration/autoland/rev/99e71b905661 Implement zstd content-encoding support r=necko-reviewers,valentin,devtools-reviewers https://hg.mozilla.org/integration/autoland/rev/ac55c45e0d0f Mark fetch zstd wpt tests as passing r=necko-reviewers,valentin
Comment 8•3 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/68f119112940
https://hg.mozilla.org/mozilla-central/rev/99e71b905661
https://hg.mozilla.org/mozilla-central/rev/ac55c45e0d0f
Comment 9•3 months ago
|
||
This needs to be documented at https://github.com/mdn/browser-compat-data/blob/ae0b3849fc709af63e04e78cdd24dc2eda22efad/http/headers/Content-Encoding.json#L100.
Sebastian
Comment 10•3 months ago
|
||
:jesup could you consider nominating this for a release note? (Process info)
Comment 11•2 months ago
•
|
||
FF126 MDN docs for this can be tracked in https://github.com/mdn/content/issues/33086.
As far as I can tell this is just a BCD entry in Content-Encoding
(done) and a release note.
Is only Content-Encoding
affected? I mean is zstd used for anything else? What about Accept-Encoding
(my assumption is that this is set by the browser, and you normally wouldn't get back zstd if you had not set this?)
Note, have marked as
dev-doc-complete
on assumption there is nothing else to say.
Updated•2 months ago
|
Assignee | ||
Comment 12•2 months ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: Significant change in what types of compression we support, impacts websites
[Affects Firefox for Android]: yes
[Suggested wording]: Firefox 126 supports Content-encoding: zstd (zstandard compression). This is an alternative to broti and gzip compression for web content, and can provide higher compression levels for the same CPU used, or conversely lower server CPU use to get the same compression. This is heavily used on sites such as Facebook. It shipped in Chrome 123 recently.
[Links (documentation, blog post, etc)]: RFC 8878, http://facebook.github.io/zstd/
Updated•2 months ago
|
Updated•20 days ago
|
Comment 14•20 days ago
|
||
Renamed so it's clear that the actual support landed in this bug.
Description
•