- From: Yves Lafon <ylafon@w3.org>
- Date: Thu, 27 Oct 2011 13:11:07 -0400 (EDT)
- To: Mark Nottingham <mnot@mnot.net>
- cc: httpbis Group <ietf-http-wg@w3.org>
On Tue, 18 Oct 2011, Mark Nottingham wrote:
As a followup, the same clarification has been added for rules based on
token or string (range-unit and acceptable-ranges).
ticket at
http://trac.tools.ietf.org/wg/httpbis/trac/ticket/319
changeset at
http://trac.tools.ietf.org/wg/httpbis/trac/changeset/1456
> On 17/10/2011, at 10:11 PM, Mark Nottingham wrote:
>
>> Currently, all of the cache-control directives (e.g., max-age) are defined as BNF strings, which means that they're case-insensitive.
>>
>> However, theoretically someone could define a directive without using a string (as we do for some other constructs, e.g., the HTTP version identifier), which means that it'd be case-sensitive.
>>
>> It seems that having such exceptions would be surprising, and that the most straightforward thing to do would be to define CC directive names as case-insensitive.
>>
>> Any thoughts? A quick check of squid2 shows it case-normalising them before comparison.
>>
>>
>> --
>> Mark Nottingham http://www.mnot.net/
>>
>>
>>
>>
>
> --
> Mark Nottingham http://www.mnot.net/
>
>
>
>
>
--
Baroula que barouleras, au tiéu toujou t'entourneras.
~~Yves
Received on Thursday, 27 October 2011 17:11:14 UTC