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: <K.Morgan@iaea.org>
Date: Wed, 26 Mar 2014 10:41:57 +0000
To: <ietf-http-wg@w3.org>
CC: <roland@zinks.de>, <phk@phk.freebsd.dk>
Message-ID: <0356EBBE092D394F9291DA01E8D28EC20100F3EFA3@sem002pd.sg.iaea.org>
> On 26.03.2014 10:48, Poul-Henning Kamp wrote:

>> In message <53329E55.5000602@zinks.de<mailto:53329E55.5000602@zinks.de>>, Roland Zink writes:

>>

>>> C-E does not allow seeks, e.g. you need to read 4G of a 8G file just

>>> to read the 100 bytes you are interested in.



This is the crux of the issue, hence the subject of this conversation!



>> That's news to me.  Range works fine with C-E in Varnish...



If Range works with C-E in Varnish, then Varnish is not HTTP/1.1 compliant.


Again, quoting the HTTP/1.1 spec, RFC2616 requires ranges to apply to the content-encoded content:
- from Section 14.35.1: "Byte range specifications in HTTP apply to the sequence of bytes in the entity-body ..."
- from Section 7.2.1: "entity-body := Content-Encoding( Content-Type( data ) )"



This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.
Received on Wednesday, 26 March 2014 10:42:33 UTC

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