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

Re: Consequences of removing the reference set

From: Martin Nilsson <nilsson@opera.com>
Date: Fri, 25 Jul 2014 21:15:57 +0200
To: "Matthew Kerwin" <matthew@kerwin.net.au>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <op.xjkigve3iw9drz@uranium>
On Fri, 25 Jul 2014 07:12:48 +0200, Matthew Kerwin <matthew@kerwin.net.au>  
wrote:

> On 25 July 2014 14:59, Martin Nilsson <nilsson@opera.com> wrote:
>> On Fri, 25 Jul 2014 01:20:28 +0200, Greg Wilkins <gregw@intalio.com>  
>> wrote:
>>
>>>
>>> In the test data there are 38037 fields in 3267 headers of which 161  
>>> have duplicate header names:
>>>
>>>     58 Duplicate: cache-control
>>>     43 Duplicate: content-type
>>>     19 Duplicate: pragma
>>>     19 Duplicate: expires
>>>      9 Duplicate: set-cookie
>>>      7 Duplicate: x-content-type-options
>>>      2 Duplicate: last-modified
>>>      2 Duplicate: content-length
>>>      2 Duplicate: accept-ranges
>>
>> In my mobile testdata I have 2086062 fields in 203586 headers with the  
>> following duplicates
>>
>> 2738 user-agent
>
>> Sorry, just so I'm reading this right, do you have 2,738 instances  
>> ​​where ​a client sent two user-agent headers in the one request?
>

Yes. Essentially all of the duplicates are prefixed SAMSUNG-GT- and both  
of them containing the same data. I don't feel this is a use case to  
optimize for.

/Martin Nilsson

-- 
Using Opera's revolutionary email client: http://www.opera.com/mail/
Received on Friday, 25 July 2014 19:16:25 UTC

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