W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2014

Re: current HTTP/2 spec prevents gzip of response to "Range" request

From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 24 Mar 2014 10:04:25 -0700
Message-ID: <CABkgnnUjXGNedAi4miJ7V3bFtMBEfkGTb8HLf7QsC6uY=zTjUg@mail.gmail.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Cc: K.Morgan@iaea.org, HTTP Working Group <ietf-http-wg@w3.org>
On 24 March 2014 09:53, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:
> Section 8.1.3. of the current draft is quite clear that implementations
> must not indicate acceptance of or support for transfer encodings using
> the `TE` header; it seems clear that `Transfer-Encoding: gzip, chunked`
> is not supposed to be used in HTTP/2.0, which is exactly the issue here.

That's because Transfer-Encoding is a hop-by-hop thing and the
non-standard "gzip" Transfer-Encoding would need to be understood by
all hops in the chain if it were to be used for ranges.  I'm not aware
of any use of Transfer-Encoding other than "chunked", because it's
virtually impossible to define a new one that interoperates.

As I said, I think that this is a confusion between two different but
oft-confused headers:

Content-Encoding: gzip
Transfer-Encoding: chunked
Received on Monday, 24 March 2014 17:04:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:25 UTC