Re: current HTTP/2 spec prevents gzip of response to "Range" request from Roland Zink on 2014-03-26 (ietf-http-wg@w3.org from January to March 2014)

From: Roland Zink <roland@zinks.de>
Date: Wed, 26 Mar 2014 11:04:48 +0100
To: ietf-http-wg@w3.org
Message-ID: <5332A640.60404@zinks.de>

On 26.03.2014 10:48, Poul-Henning Kamp wrote:
> In message <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.
> That's news to me.  Range works fine with C-E in Varnish...
>
Range works fine with C-E as long as the client retrieves the whole 
beginning of the file. If the client wants to skip some parts of it then 
it is unable to decompress. Retrieving 0-999 then 1000-1999 and so on is 
fine. But retrieving 0-999 and then 2000-2999 is a problem.

Regards,
Roland

Received on Wednesday, 26 March 2014 10:05:11 UTC