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

In message <0356EBBE092D394F9291DA01E8D28EC20100F3F0D8@sem002pd.sg.iaea.org>, K.Morgan@iaea.org wr
ites:

>> If your goal is to make HTTP the protocol that can do *everything*, then
>>you are going to get a protocol which is good for nothing.
>
>Not our goal at all.  _We just want to make sure HTTP/2 doesn't
>lock out something you can
>already do with HTTP/1.1.

So actually yes, that is your goal...

HTTP/1 is an incredibly messy protocol, and it is being abused for all
sorts of purposes, and having a goal of carrying all abuses forward,
no matter how stupid or pointless.

And I think that is a very stupid goal.

If we are not willing to cut off some of thos abuses, in exchange
for clarity and simplicity, HTTP/2.0 ain't going to be an improvement.

-- 
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 12:11:55 UTC