W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2012

Re: #307 (untangle Cache-Control ABNF)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 11 Jun 2012 14:51:38 +0200
Message-ID: <4FD5E9DA.9070200@gmx.de>
To: Mark Nottingham <mnot@mnot.net>
CC: HTTP Working Group <ietf-http-wg@w3.org>
On 2012-06-11 14:44, Mark Nottingham wrote:
> Assuming that the text isn't changing in substance, yes.
>
> I think this is verging on editorial; if anyone has concerns about this direction, please speak up; otherwise, Julian go ahead.
> ...

It's a bit more than editorial, because it tries to address the mismatch 
between the ABNFs for predefined directives (special-cased), and 
extension directives (token *and* quoted-string).

Highlighting these changes:

   Cache directives are identified by a token, to be compared case-
   insensitively, and have an optional argument, that can use both token
   and quoted-string syntax.  Recipients MUST accept both forms.

   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

     Cache-Control   = 1#cache-directive

     cache-directive = token [ "=" ( token / quoted-string ) ]

   For the cache directives defined below, no argument is defined (nor
   allowed) otherwise stated otherwise.

   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


3.2.2.2.  private

   Argument syntax:

      #field-name

   The private response directive indicates that the response message is
   intended for a single user and MUST NOT be stored by a shared cache.
   A private cache MAY store the response.

   If the private response directive specifies one or more field-names,
   this requirement is limited to the field-values associated with the
   listed response header fields.  That is, a shared cache MUST NOT
   store the specified field-names(s), whereas it MAY store the
   remainder of the response message.

   The field-names given are not limited to the set of standard header
   fields defined by this specification.  Field names are case-
   insensitive.

   Note: This usage of the word "private" only controls where the
   response can be stored; it cannot ensure the privacy of the message
   content.  Also, private response directives with field-names are
   often handled by implementations as if an unqualified private
   directive was received; i.e., the special handling for the qualified
   form is not widely implemented.

   Note: For compatibility with non-robust recipients, even a single-
   entry list of field names SHOULD be sent using the quoted-string
   syntax.

   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

   ....

Best regards, Julian
Received on Monday, 11 June 2012 12:52:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 11 June 2012 12:52:32 GMT