On Wed, 31 Oct 2018, Jan Stary wrote:

>> I also looked at the relevant HTTP spec [2], which says (paraphrasing) that
>> a request without any Accept-Encoding headers means the server can send any
>> Content-Encoding in response. Personally, I think that if the client side
>> is capable of decoding the encoding, it should attempt to do so, as that
>> provides the most useful default.
>
> Yes.

Strictly speaking and protocol-wise, the header just tells the client that the
content is compressed. It doesn't mean "please uncompress this". Even if
that's what some clients do and I'm sure some servers want to imply when
sending that header...

-- 
  / daniel.haxx.se
-----------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users
Etiquette:   https://curl.haxx.se/mail/etiquette.html