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

Re: HPACK opcode bit patterns

From: Michael Sweet <msweet@apple.com>
Date: Wed, 06 Aug 2014 20:41:48 -0400
Cc: Jason Greene <jason.greene@redhat.com>, David Krauss <potswa@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-id: <489B12BE-F5FC-44B7-B436-52591FFF9632@apple.com>
To: Greg Wilkins <gregw@intalio.com>
Greg,

On Aug 6, 2014, at 6:22 PM, Greg Wilkins <gregw@intalio.com> wrote:
> ...
> Jetty pretty much has the same.   However I'm thinking that we will index Date as we often see batches of messages sent within the same second.

I thought the same, but when I index Date the header table gradually fills with Date headers and you eventually see (well, sort of) all of the headers "marching out" as new Date headers are added. That leads to re-indexing of the lost non-Date headers, etc.

> We are also currently never indexing set-cookie, but I admit to be confused about the need to do this or if it can just be without index?

You could decide based upon the use/requirement of https for the cookie - at least then you are protecting (never index) data that is normally encrypted vs. allowing indexing for cleartext...

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair




Received on Thursday, 7 August 2014 00:42:16 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:10 UTC