- From: John Simpson <john@consumerwatchdog.org>
- Date: Wed, 10 Oct 2012 15:21:52 -0700
- To: Shane Wiley <wileys@yahoo-inc.com>
- Cc: Jonathan Mayer <jmayer@stanford.edu>, "public-tracking@w3.org" <public-tracking@w3.org>
- Message-Id: <59A54C74-3AEB-4F2C-912C-AF3B56C3DA4A@consumerwatchdog.org>
Shane, What would be the reason for acting as if no DNT header had been received if they conflict? I'd think if there were a conflict, the consumer/privacy friendly approach would be to assume the user meant to send DNT:1 and somehow misconfigured the UA. In other words, proceed with caution until you clearly determine what the user intended. That's why the best practice would be to inform the user of a possible problem. Best, John ---------- John M. Simpson Consumer Advocate Consumer Watchdog 2701 Ocean Park Blvd., Suite 112 Santa Monica, CA,90405 Tel: 310-392-7041 Cell: 310-292-1902 www.ConsumerWatchdog.org john@consumerwatchdog.org On Oct 10, 2012, at 2:59 PM, Shane Wiley wrote: > Alternate Text for Conflicting Headers: > > If a server receives conflicting DNT headers, it MAY choose to treat the transaction as if no DNT header had been received. The Server MAY choose to alert the user about possible user agent configuration issues causing multiple, conflicting DNT header signals to be received. > > From: Jonathan Mayer [mailto:jmayer@stanford.edu] > Sent: Wednesday, October 10, 2012 2:46 PM > To: public-tracking@w3.org > Subject: Multiple DNT Headers (ACTION-283, ISSUE-150) > > Proposed text on duplicate headers: > > If a server receives duplicate DNT headers, it MUST act as if it had received a single DNT header. > > Proposed text on conflicting headers: > > If a server receives conflicting DNT headers, it MUST act as if it had received a single DNT: 1 header. It is a best practice for the server to alert the user about possible user agent misconfiguration. >
Received on Wednesday, 10 October 2012 22:21:55 UTC