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: <K.Morgan@iaea.org>
Date: Thu, 27 Mar 2014 21:03:58 +0000
To: <roland@zinks.de>, <ietf-http-wg@w3.org>
CC: <C.Brunhuber@iaea.org>
Message-ID: <0356EBBE092D394F9291DA01E8D28EC20100F401B8@sem002pd.sg.iaea.org>
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)?
This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.
Received on Thursday, 27 March 2014 21:04:30 UTC

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