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: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Mon, 24 Mar 2014 17:53:26 +0100
To: Martin Thomson <martin.thomson@gmail.com>
Cc: K.Morgan@iaea.org, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <q8o0j9picqc6ode3v9v3g1uqgtd5dhi02q@hive.bjoern.hoehrmann.de>
* Martin Thomson wrote:
>I think perhaps that you have Transfer-Encoding confused with Content-Encoding.
>HTTP/2 does not change the characteristics of the protocol with
>respect to ranges.  We do change Content-Encoding to requirement that
>the client support gzip, but this doesn't affect the case you

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.
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Monday, 24 March 2014 16:54:02 UTC

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