W3C home > Mailing lists > Public > public-tracking-comments@w3.org > August 2015

Re: CR: Tracking Preference Expression (DNT)

From: David Singer <singer@apple.com>
Date: Wed, 26 Aug 2015 12:09:12 +0900
Cc: public-tracking-comments@w3.org
Message-id: <CFCCB454-16CE-4DDE-BBD8-E28333B047E6@apple.com>
To: timeless <timeless@gmail.com>
Hi, thanks for the comments.  one quick one:

> On Aug 26, 2015, at 10:24 , timeless <timeless@gmail.com> wrote:
> 
>> At most one DNT header field can be present in a valid request.
> 
> `can` isn't rfc speak

I think it’s a statement of what is possible; HTTP 1.1 only allows multiple header fields in cases that don’t apply here, so the restriction is not this spec., but HTTP 1.1.  ‘can’ is therefore expressing a truth, rather than ‘may’ which would be expressing a permission.

"Multiple message-header fields with the same field-name MAY be present in a message if and only if the entire field-value for that header field is defined as a comma-separated list [i.e., #(values)]. It MUST be possible to combine the multiple header fields into one "field-name: field-value" pair, without changing the semantics of the message, by appending each subsequent field-value to the first, each separated by a comma. The order in which header fields with the same field-name are received is therefore significant to the interpretation of the combined field value, and thus a proxy MUST NOT change the order of these field values when a message is forwarded.” [http rfc]

David Singer
Manager, Software Standards, Apple Inc.
Received on Wednesday, 26 August 2015 03:09:46 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 26 August 2015 03:09:47 UTC