cURL / Mailing Lists / curl-users / Single Mail


Re: --tr-encoding and HTTP/2

From: Daniel Stenberg <>
Date: Mon, 31 Oct 2016 15:05:42 +0100 (CET)

On Sun, 30 Oct 2016, Ricki Hirner wrote:

>    The only exception to this is the TE header field, which MAY be
>    present in an HTTP/2 request; when it is, it MUST NOT contain any
>    value other than "trailers".
> Didn't see that before. Does that mean that HTTP/2 doesn't have useful
> compression (= transparent compression that doesn't change the ETag)
> anymore?

First, Transfer-Encoding was never used widely (like for example by the
mainstream browsers) and because of that it was never made working properly
across the Internet. That's then why everyone remains using Content-Encoding
for automatic compression even though it was transfer-encoding that made for
this purpose.

> Wow, thanks Google …

I don't see why Google can be blamed for that.


List admin:
Received on 2016-10-31