W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2014

Re: h2#404 requiring gzip and/or deflate

From: Zhong Yu <zhong.j.yu@gmail.com>
Date: Fri, 21 Mar 2014 16:39:35 -0500
Message-ID: <CACuKZqHubB6+TzDDFAJa81fYWKxkOLrJ9BME_z3dmQ_MZemJ=g@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Patrick McManus <mcmanus@ducksong.com>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
On Fri, Feb 21, 2014 at 11:13 AM, Martin Thomson
<martin.thomson@gmail.com> wrote:
> On 21 February 2014 05:08, Patrick McManus <mcmanus@ducksong.com> wrote:
>> I think what the http/2 text means to say is that an "Accept-Encoding: gzip,
>> deflate" request header is implicit in every request and the client needs to
>> be able to process responses with those encodings.
>
>
> Yes, that is the implication.  Even if you include "Accept-Encoding:
> rot13", you effectively get *either* "Accept-Encoding: rot13,
> identity, gzip, deflate" or "Accept-Encoding: rot13, identity, gzip".
> This is a change from 1.1, which implies "Accept-Encoding: rot13,
> identity" only.

What if the request has

    Accept-Encoding: gzip;q=0

Can server ignore that directive and send gzip-ed response anyway?


>
> I had inferred the gzip+deflate, but Mark points out that this could
> also be interpreted as the latter.  Hence this thread requesting
> clarification.
>
> I hope that I'm not completely off-base on this.  No one wants to
> remove this entirely and revert to "identity" only, do they?
>
Received on Friday, 21 March 2014 21:40:03 UTC

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