Re: Header Table and Static Table Indicies Switched

• From: Jeff Pinner <jpinner@twitter.com>
• Date: Sat, 2 Aug 2014 08:31:14 -0700
• To: Greg Wilkins <gregw@intalio.com>
• Cc: HTTP Working Group <ietf-http-wg@w3.org>
• Message-ID: <CA+pLO_jNTL3c8gjkJ=8v-W+M3s+UO=ii=ii=JDXtNyKc75EhuQ@mail.gmail.com>

> If static header names are more frequent than custom ones (as you would
> expect them to be), then I think this result will be pretty much the same on
> most data sets.

This is my point, they are only more frequent on "public" data sets
since you are getting web browser requests that have to interop with
every website. For APIs or internal requests that is very referenced.

And for those that do appear, they will be indexed and thus get a lower index.

Consider this, for a client encoding requests, there is no reason to
use the index space for response header names that will NEVER be sent.
Putting the header table below the static table moves those request
headers that are indexed below the static table, pushing the response
names to a higher value.

Received on Saturday, 2 August 2014 15:31:41 UTC