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

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Wed, 26 Mar 2014 10:22:37 +0000
To: Roland Zink <roland@zinks.de>
cc: ietf-http-wg@w3.org
Message-ID: <2555.1395829357@critter.freebsd.dk>

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 ?

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

Received on Wednesday, 26 March 2014 10:23:00 UTC