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

Re: h2#404 requiring gzip and/or deflate

From: Roberto Peon <grmocg@gmail.com>
Date: Fri, 21 Feb 2014 09:38:03 -0800
Message-ID: <CAP+FsNegPS+HGrQgQBD6jB+GUwtHduQkMyJ7Jz06rCDeWqPW0w@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>, Patrick McManus <mcmanus@ducksong.com>
No. Reverting to solely identity would be a huge step backwards.
On Feb 21, 2014 9:17 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.
>
> 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 February 2014 17:38:30 UTC

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