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: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Wed, 26 Mar 2014 11:01:09 +0000
To: Roland Zink <roland@zinks.de>
cc: ietf-http-wg@w3.org
Message-ID: <2853.1395831669@critter.freebsd.dk>
In message <5332AFD6.1000105@zinks.de>, Roland Zink writes:

>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.

The logfile example I'm just going to ignore because it is bogus on
so many planes that it's not even funny:  The exact same problem
exists with compressed logfiles when no HTTP is involved at alle.

Video formats defined exactly so that they are searchable, and if
anybody wastes their time gzip'ing videos, they have bigger problems
than not being able to search them.

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 11:01:33 UTC

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