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

> Also, multipart/byteranges may carry a gzip-ed range, though
> multipart/byteranges is probably not well supported.

I take it back - not sure about the semantics if a part in a
multipart/byteranges contains header "Content-Encoding: gzip". It'll
probably be ignored by most implementation.

Zhong Yu

Received on Monday, 24 March 2014 15:40:16 UTC