Conversation
The HTTP `deflate` content coding is the zlib format (RFC 1950, per RFC 9110 section 8.4.1.2), which on-the-fly compression sends with static-web-server/static-web-server#764. Link it instead of the raw DEFLATE format (RFC 1951).
This branch has not been deployed
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.
Description
features/compression.md(v3) linkedDeflateto RFC 1951, the raw DEFLATE format. The HTTPdeflatecontent coding is the zlib format, RFC 1950 (RFC 9110, section 8.4.1.2), which on-the-fly compression sends with static-web-server/static-web-server#764 (issue static-web-server/static-web-server#763). This changes only the link target.The v2 page is left as is, since
2.xstill sends raw DEFLATE unless the fix is backported.Please merge this together with (or after) the code PR.
markdownlint-cli2andprettier --checkpass.