Feature request: zstd compression

[fili]

Would be nice to have this added.

See also https://groups.google.com/a/chromium.org/g/blink-dev/c/GDsI0Hw-jYk/m/AsQS-km-DQAJ and https://chromestatus.com/feature/6186023867908096

[antoni-szych-rtbhouse]

Note that zstd support is supposedly landing in stable chrome v.123 on Mar 13, 2024.
However for example my system logs show that some global switch was turned on on 22 Feb 2024 and versions as "old" as chrome v.121 started asking for zstd-compressed data. Earlier there was a little bit of beta-users traffic, however it was nothing compared to the volumes seen from 22 Feb.

22 Feb -> 25% of the traffic had zstd support enabled
23 Feb -> 40% of the traffic had zstd support enabled
26 Feb -> 60% of the traffic had zstd support enabled

[alexprengere]

It looks like zstd support has landed in httpx, and they settled on the zstandard python package (there are multiple implementations on PyPI).

[fili]

See also Mozilla's latest update.

[alexprengere]

Cf #45

[alexprengere]

The PR has been merged and the release done on PyPI.

[alexprengere]

Small heads up, as the zstd algorithm is now placed before br in the defaults, installing the latest flask-compress will prefer zstd to brotli on Chrome 123+.

Note that zstd is not always preferable to brotli, it highly depends on the type of traffic served. There are lots of resources comparing the two.