Re: Support for gzip at the server #424 (Consensus Call)

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.

Received on Friday, 21 March 2014 19:13:19 UTC