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: Roland Zink <roland@zinks.de>
Date: Wed, 26 Mar 2014 11:45:42 +0100
Message-ID: <5332AFD6.1000105@zinks.de>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
CC: ietf-http-wg@w3.org
Looks like there is the log file example mentioned in the discussion. 
Where this is often used is in playing videos (although there often no 
gzip is used but I have seen this too). Many players allow the user to 
jump within the video.


On 26.03.2014 11:22, Poul-Henning Kamp wrote:
> In message <5332A640.60404@zinks.de>, Roland Zink writes:
>> 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.
> Can you give an example of a real-world application where this is anything
> but a minor inconvenience ?
Received on Wednesday, 26 March 2014 10:46:05 UTC

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