ISSUE-110: Is top-level-origin for outgoing requests workable for site-specific tracking exceptions?
Is top-level-origin for outgoing requests workable for site-specific tracking exceptions?
- State:
- CLOSED
- Product:
- Tracking Preference Expression (DNT)
- Raised by:
- Nick Doty
- Opened on:
- 2012-01-06
- Description:
- Will all implementers, including browser extensions, be able to determine the corresponding top-level-origin for all outgoing requests in order to handle site-specific tracking exception pairs?
See "Behavior for future requests with site-specific exceptions". - Related Actions Items:
- No related actions
- Related emails:
- Re: ISSUE-111 - Exceptions are broken (from jmayer@stanford.edu on 2012-03-13)
- RE: ISSUE-111 - Exceptions are broken (from jccannon@microsoft.com on 2012-03-12)
- Re: ISSUE-111 - Exceptions are broken (from sid@mozilla.com on 2012-03-12)
- RE: ISSUE-111 - Exceptions are broken (from kevsmith@adobe.com on 2012-03-09)
- RE: ISSUE-111 - Exceptions are broken (from wileys@yahoo-inc.com on 2012-03-08)
- Re: ISSUE-111 - Exceptions are broken (from jmayer@stanford.edu on 2012-03-08)
- Re: ISSUE-111 - Exceptions are broken (from jmayer@stanford.edu on 2012-03-08)
- RE: ISSUE-111 - Exceptions are broken (from kevsmith@adobe.com on 2012-03-08)
- Re: ISSUE-111 - Exceptions are broken (from npdoty@w3.org on 2012-03-08)
- diff of TPE editing since the FPWD (from fielding@gbiv.com on 2012-01-10)
- tracking-ISSUE-110: Is top-level-origin for outgoing requests workable for site-specific tracking exceptions? [Tracking Preference Expression (DNT)] (from sysbot+tracker@w3.org on 2012-01-06)
Related notes:
No additional notes.
Display change log