curl / Mailing Lists / curl-users / Single Mail


Re: Proposal to change default handling for content-encoded responses

From: Daniel Stenberg <>
Date: Wed, 31 Oct 2018 22:19:59 +0100 (CET)

On Wed, 31 Oct 2018, Jan Stary wrote:

>> Strictly speaking and protocol-wise, the header just tells the client that
>> the content is compressed.
> At the risk of splitting hair, it tells the client
> that the server _has_compressed_ the content it is sending, right?

No. Content-Encoding describes the content, it says nothing about who did it
nor when the encoding was done or even for what purpose. Automatic
decompression of this for transfer purposes was always a bit of an abuse of
HTTP since the original intent was to use transfer-encoding for that. But
nobody (except curl and some rare clients) implements that and everyone just
sticks to the Content-Encoding header...

Received on 2018-10-31