- From: Martin Nilsson <nilsson@opera.com>
- Date: Thu, 25 Oct 2012 13:36:54 +0200
- To: "Roberto Peon" <grmocg@gmail.com>
- Cc: ietf-http-wg@w3.org
On Tue, 23 Oct 2012 17:29:28 +0200, Roberto Peon <grmocg@gmail.com> wrote: > What Martin said... with special emphasis on the difficulty of sanitizing > the headers. :) > One way that perhaps is possible is to split the request headers into three groups, user agent-specific (accept, host, user-agent etc), network-specific (x-up-calling-line-id, x-msisdn etc) and site-specific (cookie). Processing of captured data can then generate rules for how to generate the headers for each set (Nokia5130c-2 device, AT&T no privilege network, Google search logged in repeat visit). And immediately I realized that there are cross over issues, like the cookie header both being a site specific header, with user-agent specific formatting, as well as possibly added by the network equipment for specific destinations... /Martin Nilsson -- Using Opera's revolutionary email client: http://www.opera.com/mail/
Received on Thursday, 25 October 2012 11:37:26 UTC