Edit ISSUE-106: Response header on cacheable objects?

Nickname:

Title:

State:

Product:

Raised By:

Description:

Add notes (no markup allowed, URIs get automatically hyperlinked):

Related emails:

  1. PENDING REVIEW: Proposal to close a series of PENDING REVIEW Items (from mts@zurich.ibm.com on 2012-02-21) (from mts@zurich.ibm.com on 2012-02-21)
  2. Re: ACTION-114 ISSUE-107 : Revised response header. (from ktrilli@truste.com on 2012-02-08) (from ktrilli@truste.com on 2012-02-08)
  3. RE: ISSUE-106: Responses on cached objects (from wileys@yahoo-inc.com on 2012-02-07) (from wileys@yahoo-inc.com on 2012-02-07)
  4. ISSUE-106: Responses on cached objects (from mts@zurich.ibm.com on 2012-02-07) (from mts@zurich.ibm.com on 2012-02-07)
  5. Re: ACTION-114 ISSUE-107 : Revised response header. (from sharvey@google.com on 2012-02-05) (from sharvey@google.com on 2012-02-05)
  6. Re: ACTION-114 ISSUE-107 : Revised response header. (from sharvey@google.com on 2012-02-05) (from sharvey@google.com on 2012-02-05)
  7. ACTION-114 ISSUE-107 : Revised response header. (from tom@mozilla.com on 2012-02-03) (from tom@mozilla.com on 2012-02-03)
  8. Re: Revised Response Header (from tom@mozilla.com on 2012-01-26) (from tom@mozilla.com on 2012-01-26)
  9. RE: Revised Response Header (from kevsmith@adobe.com on 2012-01-25) (from kevsmith@adobe.com on 2012-01-25)
  10. Re: Revised Response Header (from tom@mozilla.com on 2012-01-25) (from tom@mozilla.com on 2012-01-25)
  11. Re: Revised Response Header (from singer@apple.com on 2012-01-25) (from singer@apple.com on 2012-01-25)
  12. Re: Revised Response Header (from singer@apple.com on 2012-01-25) (from singer@apple.com on 2012-01-25)
  13. Revised Response Header (from tom@mozilla.com on 2012-01-25) (from tom@mozilla.com on 2012-01-25)
  14. Agenda for 2012-1-17 call (from mts@zurich.ibm.com on 2012-01-17) (from mts@zurich.ibm.com on 2012-01-17)
  15. diff of TPE editing since the FPWD (from fielding@gbiv.com on 2012-01-10) (from fielding@gbiv.com on 2012-01-10)
  16. tracking-ISSUE-106: Response header on cacheable objects? [Tracking Preference Expression (DNT)] (from sysbot+tracker@w3.org on 2011-12-19) (from sysbot+tracker@w3.org on 2011-12-19)

Related notes:

Agreement was YES. Reasoning: Cacheable resources can be used for tracking by creating individualised URLs that are only accessed by one user. This would allow tracking and therefore, non-tracking needs to be declared.

Matthias Schunter, 20 Feb 2012, 10:16:45

2012-02-21: We agreed that cacheable resources may be used for tracking (through personalized URLs) and thus should include a response header (or be covered by any other feedback mechanism we design).

Text in current draft:
http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html


I did not receive any feedback on this section and I plan to change the status of this issue to CLOSED.

Matthias Schunter, 21 Feb 2012, 16:31:43

2012-02-21: Proposal to close sent
2012-02-27: No objections received -> Closing the issue

Matthias Schunter, 27 Feb 2012, 15:52:53


Matthias Schunter <matthias.schunter@intel.com>, Chair, Bert Bos <bert@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $