W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2013

Re: I ran across this while working on the spec.

From: Fred Akalin <akalin@google.com>
Date: Wed, 16 Oct 2013 19:09:55 -0700
Message-ID: <CANUYc_RnRyumExZFz5kwCi=7338T3rT-sS-j-Qi9eU731CuPXg@mail.gmail.com>
To: Roberto Peon <fenix@google.com>
Cc: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
(copying from issue)

#1 <https://github.com/http2/http2-spec/issues/1> has the problem that it
introduces an ambiguity in what to do when reducing the max size (clear out
the reference set first?). But if we specify exactly what to do when
reducing the max size, then that isn't that bad.

On Wed, Oct 16, 2013 at 5:37 PM, Roberto Peon <fenix@google.com> wrote:

> https://github.com/http2/http2-spec/issues/281
> Setting the max header size to 0 does not clear out all encoder state.
> In particular, elements to the reference set that are pointing to static
> table elements are not cleared out.
> There are a couple of obvious ways of fixing this:
> 1) Include the space used in the reference set in the overhead (e.g.
> 2-bytes per reference)
> 2) explicit SETTING for clearing the compression state
> I prefer #1.
Received on Thursday, 17 October 2013 02:10:24 UTC

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