- From: Tracking Protection Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Thu, 09 Aug 2012 22:02:16 +0000
- To: public-tracking@w3.org
tracking-ISSUE-158 (redirects): What is the effect of re-directs for content on the operation of exceptions? [Tracking Preference Expression (DNT)] http://www.w3.org/2011/tracking-protection/track/issues/158 Raised by: David Singer On product: Tracking Preference Expression (DNT) Let's say that a site, ExampleNews.com, has negotiated with a user to allow tracking on the site, in return for free access. The user consented, and the site set up an explicit site-specific exception by calling the API; let's say it was for ExampleAds.com and ExampleAnalytics.com. This means that ExampleAds.com and ExampleAnalytics.com will get DNT:0 headers from the user's browser. Now, let's look at the page; it loads ads from both ExampleAdAggregator.com and ExampleAds.com. ExampleAdAggregator.com was NOT named in the exception API call, so it gets DNT:1. But now the questions: 1. For some reason, in this case, ExampleAds.com decides to load content from yet another Ad service; it does a re-direct to AdSample.com. Does AdSample.com get (a) the DNT:1 that it gets because it was not requested in the API or (b) DNT:0 as passed in the original HTTP request to ExampleAds.com, which got re-directed here? 2. ExampleAdAggregator does an HTTP re-direct to ExampleAds.com! Now, does ExampleAds.com get (a) the DNT:0 it should get as as requested in the API or (b) DNT:1 as passed to the original ad request to ExampleAdAggregator, which got re-directed here? At the moment, the text says that (a) applies, i.e. the explicit list rules and re-directs are not relevant.
Received on Thursday, 9 August 2012 22:02:17 UTC