Cool, Catching up here (sorry, too many threads) Does this issue or another deal with the response header and intermediaries? Because I think the response header is a MUST NOT fiddle with, for intermediaries, as it's the only opportunity for the end-point to be aware of actual state. On Nov 30, 2011, at 9:57 , Shane Wiley wrote: > Here is a draft for Issue-95 (http://www.w3.org/2011/tracking-protection/track/issues/95): > > “Generally, the setting and/or unsetting of a Do Not Track signal SHOULD only be established by a user proactively. Intermediaries to an HTTP/S request SHOULD NOT attempt to modify the DNT signal in any way. There are limited situations where it MAY be appropriate for an intermediary to modify a user’s DNT settings on their behalf such as through employer networks or public networks (libraries, for example). But, care should be taken even in these cases to limit the scope of modification as much as possible to decrease the possible impact to a user’s web surfing experience as overriding DNT signals could disrupt content consumption through user granted site-specific exceptions. NOTE – it is understood this particular compliance standard cannot be technically enforced but it should be clear to all web ecosystem participants what the standard baseline is in this matter.” David Singer Multimedia and Software Standards, Apple Inc.
Received on Wednesday, 14 December 2011 22:59:05 UTC