ISSUE-264: requirement on UAs for setting cookies

requirement on UAs for setting cookies

State:
PENDING REVIEW
Product:
TPE Last Call
Raised by:
Xuemei Yan
Opened on:
2014-07-13
Description:
http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/att-0013/comments_on_working_draft_of_tracking_preference_expression_DNT_.doc

Comment: A user agent MUST NOT block the transmission of any Cookie, also MUST NOT block the operation of setting cookie upon the receipt of any request. Reason: In general, A user agent will configurate an option for user to close the cookie. If removal of the cookie, the internet service can not be used in normal condition.
Related Actions Items:
No related actions
Related emails:
  1. Re: tracking-ISSUE-264: requirement on UAs for setting cookies [TPE Last Call] (from fielding@gbiv.com on 2014-09-09)
  2. RE: tracking-ISSUE-264: requirement on UAs for setting cookies [TPE Last Call] (from michael.oneill@baycloud.com on 2014-07-13)
  3. Re: tracking-ISSUE-264: requirement on UAs for setting cookies [TPE Last Call] (from walter.van.holst@xs4all.nl on 2014-07-13)
  4. tracking-ISSUE-264: requirement on UAs for setting cookies [TPE Last Call] (from sysbot+tracker@w3.org on 2014-07-13)

Related notes:

WONTFIX. This comment has nothing to do with TPE.

How a user agent is configured to send (or not send) Cookies is defined by the Cookie RFC and HTTP/1.1. In general, the choice of sending Cookie header fields is left to the user agent configuration, since the right balance between privacy and site (dys)function can only be chosen by the user. A user can make such choices independent of their DNT configuration.

Roy Fielding, 10 Sep 2014, 00:11:49

Display change log ATOM feed


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.325 2014-09-10 21:42:02 ted Exp $