Refactor GzipHandler into DynamicCompressionHandler and allow ServiceLoader to find other implementations

[joakime]

Jetty version(s) Jetty 12

Enhancement Description The current GzipHandler does a good job at handling Content-Encoding: gzip (and Accept-Encoding: gzip), but we shouldn't hardcode only gzip support.

Can we refactor the existing GzipHandler to be more generic, something like DynamicCompressionHandler and have the Gzip support (courtesy of the existing GzipRequest object) just be loaded via a ServiceLoader?

This way we can encourage other compression algorithms under the same Accept-Encoding / Content-Encoding / already compressed rules that the existing codebase handles for us?

Other compression algorithms that have been requested in our issue tracker.

• 2553 - RFC 7932 - Brotli Compressed Data Format

• 6600 - RFC 8878 - Zstandard Compression and the application/zstd Media Type

(FYI, curl supports both of these compression types now)

[github-actions[bot]]

This issue has been automatically marked as stale because it has been a full year without activity. It will be closed if no further activity occurs. Thank you for your contributions.

[joakime]

When we do this we need to keep in mind the effort for Compression Dictionary Transport.

• https://github.com/WICG/compression-dictionary-transport
• https://datatracker.ietf.org/doc/draft-ietf-httpbis-compression-dictionary/
• https://chromestatus.com/feature/5124977788977152

[gregw]

@joakime lets start working on this in the 12.1.x branch

[joakime]

I'm working on this now.