Why not set CURLOPT_ACCEPT_ENCODING?

[tecosaur]

After setting Accept-Encoding manually and being surprised to get uncompressed output (I had assumed curl would "just" decompress it), I've come across CURLOPT_ACCEPT_ENCODING.

Using it with a custom Downloader and setopt, this seems to work a treat, and like something that could be worth setting for the default downloader unless there's some major drawback I'm missing.

[tecosaur]

It seems this can be closed in light of #93, though it has been in limbo for the past ~4 years.

[StefanKarpinski]

I'm sorry, I'm kind of missing the TLDR here? It seems to me that we would want to set accept encoding to allow compression formats that we can actually transparently decode so that the server can use them. We could do this by default for the compression formats that we can handle. The observable behavior would be unchanged since the content would be the uncompressed data, it would just be more efficient to send it.