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

RE: HTTP Header Compaction Results

From: RUELLAN Herve <Herve.Ruellan@crf.canon.fr>
Date: Thu, 25 Oct 2012 08:09:00 +0000
To: Mark Nottingham <mnot@mnot.net>
CC: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <6C71876BDCCD01488E70A2399529D5E522F9AC@ADELE.crf.canon.fr>

> -----Original Message-----
> From: Mark Nottingham [mailto:mnot@mnot.net]
> Sent: mercredi 24 octobre 2012 07:26
> To: RUELLAN Herve
> Cc: ietf-http-wg@w3.org
> Subject: Re: HTTP Header Compaction Results
> > Currently we are using web pages obtained from Alexa's top ranked sites.
> While computing our results, we are taking into account several parameters:
> separate study of requests and responses, using deflate or not (when
> relevant), variable number of exchanged messages (corresponding to
> loading from 1 to 10 web pages). Any advice on these measurements would
> be appreciated.
> For the time being, mine combines all of the requests / responses on
> different connections to the same server into the same file, under the
> assumption that multiplexing will enable this. Eventually I'd like to get
> something more sophisticated in there.
> It also removes connection headers, as they're really HTTP/1 specific.
> What else should we be doing?

On our side, we use har files, that are generated directly by Chrome. In one har file, we have all the requests/responses to all the servers necessary to load a set of web pages. The web pages themselves come from only one server. We therefore have to do some processing to split the requests/responses according to their target server.

We've not yet implemented any specific filtering on the headers, but should probably do this to remove connection headers for example.


Received on Thursday, 25 October 2012 08:09:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:07 UTC