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

Re: ezflate: proposal to reinstitute deflate header compression

From: Willy Tarreau <w@1wt.eu>
Date: Tue, 3 Jun 2014 17:21:20 +0200
To: RUELLAN Herve <Herve.Ruellan@crf.canon.fr>
Cc: "K.Morgan@iaea.org" <K.Morgan@iaea.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, "C.Brunhuber@iaea.org" <C.Brunhuber@iaea.org>
Message-ID: <20140603152120.GJ3154@1wt.eu>
On Tue, Jun 03, 2014 at 08:45:16AM +0000, RUELLAN Herve wrote:
> > -----Original Message-----
> > From: Willy Tarreau [mailto:w@1wt.eu]
> > Sent: mardi 3 juin 2014 10:18
> > To: K.Morgan@iaea.org
> > Cc: ietf-http-wg@w3.org; C.Brunhuber@iaea.org
> > Subject: Re: ezflate: proposal to reinstitute deflate header compression
> >
> > ...
> > 
> > it yet so I would not pronounce myself on it), but at least it has the merit
> > of having been designed for the exact purpose it will be used for. My only
> > concern with it is how we could disable it when its gains are not considered
> > worth its costs, or when an issue is faced later and we need to disable it.
> 
> HPACK in itself can't be disabled, but you can always send headers as
> literals and flagging them to forbid indexation further down the path. You
> can do this for all headers, to go back to an encoding close to HTTP/1.x, or
> only for some critical headers.
> This feature was added recently, after a security analysis of HPACK.

OK, thank you Hervé for this clarification.

Regards,
Willy
Received on Tuesday, 3 June 2014 15:22:19 UTC

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