- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 21 Mar 2014 21:21:35 +0100
- To: Martin Thomson <martin.thomson@gmail.com>, Roland Zink <roland@zinks.de>
- CC: HTTP Working Group <ietf-http-wg@w3.org>
On 2014-03-21 20:12, Martin Thomson wrote: > On 21 March 2014 01:37, Roland Zink <roland@zinks.de> wrote: >> I have a concern about this in the presence of range requests / responses. >> Assuming there is a HTTP/1.1 to HTTP/2 gateway and a client supporting range >> requests but not gzip. The gateway can't decompress a potential range >> response when the start isn't included. What should the gateway do to a ETag >> header when it needs to decompress? > > Sounds like a perfect case to apply 415 to. ETag would (I imagine) be > the same regardless of whether gzip is applied. The Etag will need to be different, as it is a different entity. Best regards, Julian
Received on Friday, 21 March 2014 20:22:08 UTC