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

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.

Roland


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