Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
TODO: Support Multiple Content-Encodings #2002
RFC 7231 Section 184.108.40.206 allows multiple encodings for a single request. Adding this feature may result in lower bandwidth and promotes a more resource-friendly web. Currently, Chrome and Firefox support multiple encodings for requests.
For reference, here are a few examples:
Can you show me a single resource anywhere that gets smaller by using multiple encodings? Multiple ones don't help, they just complicate matters. But since the browsers support this, I think curl should too. I don't consider it terribly important though as I've never seen such a resource and it can still be fixed after the fact on downloaded content.
The home pages of Facebook, Yahoo, Twitter, and YouTube would all take up less bandwidth when compressed with
I totally agree here, it does make debugging and requests a bit more complicated.
I agree here as well, not at all a pressing issue. I believe we don't see multiple encodings in the wild because of the following reasons:
If we fix the first issue more web servers will be able to take advantage. One way web servers can take advantage is by determining the right amount of compression before hand, then sending the response that would provide the best results.
How on earth does that make sense? Why would compressing gzip again - with gzip - make anything smaller?
Besides, I wasn't asking for that. I was asking for existing web resources that use double-encoding.
Personally, I think adding support for brotli is a way better investment in time and energy and will make even better compression utilized...