Skip to content

Support zstd Content-Encoding #50643

Open
@manandre

Description

@manandre

Is there an existing issue for this?

  • I have searched the existing issues

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

  • Support zstd as the token from the Content-Encoding header in the request.
  • Decompress with Zstandard the request content.

Response compression

  • Support zstd as a token from the Accept-Encoding header in the request.
  • Compress with Zstandard when the zstd token is elected as response compression, and so stored in the Content-Encoding header in the response.

Zstandard implementation

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-middlewareIncludes: URL rewrite, redirect, response cache/compression, session, and other general middlewaresblockedThe work on this issue is blocked due to some dependency

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions