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

On 27.03.2014 22:03, K.Morgan@iaea.org wrote:
> On 26 March 2014 19:18, Roland Zinks wrote:
>> I like the idea of requiring transfer encoding instead of content encoding but I have concerns regarding
>> replacing content-encoding by transfer encoding...
> Understood.
>
>> Mandating content-encoding gzip has the same issue as it is not mandated in HTTP/1.1 and a gateway
>> can't really translate.
> Not sure what you mean exactly.  Isn't that how Section 9.3 of the current draft is written (i.e. content-encoding: gzip is explicitly supported on every request)?
>
Yes it is written this way and this is a problem for a gateway from my 
point of view.

Received on Friday, 28 March 2014 09:10:16 UTC