Support zstd Content-Encoding #50643
Labels
area-middleware
Includes: URL rewrite, redirect, response cache/compression, session, and other general middlesware
blocked
The work on this issue is blocked due to some dependency
Milestone
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
No response
Describe the solution you'd like
Zstandard, or
zstd
, is a data compression mechanism described in RFC8878. It is a fast lossless compression algorithm, targeting real-time compression scenarios at zlib-level and better compression ratios. The "zstd" token was added as an IANA-registered Content-Encoding token as per https://datatracker.ietf.org/doc/html/rfc8878#name-content-encoding.The Facebook/Zstd team has published some of their research on compression level vs. CPU vs. compression ratio.
Current support
Features request
Request compression
zstd
as the token from theContent-Encoding
header in the request.Response compression
zstd
as a token from theAccept-Encoding
header in the request.zstd
token is elected as response compression, and so stored in theContent-Encoding
header in the response.Zstandard implementation
Additional context
No response
The text was updated successfully, but these errors were encountered: