W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2011

Re: Cache-Control directive case sensitivity

From: David Morris <dwm@xpasc.com>
Date: Mon, 17 Oct 2011 08:44:33 -0700 (PDT)
To: Julian Reschke <julian.reschke@gmx.de>
cc: Mark Nottingham <mnot@mnot.net>, httpbis Group <ietf-http-wg@w3.org>
Message-ID: <Pine.LNX.4.64.1110170842080.9959@egate.xpasc.com>


On Mon, 17 Oct 2011, Julian Reschke wrote:

> On 2011-10-17 13:11, 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.
> 
> +1, and we probably should mention that as part of #231 for parameter names.

++1 ... I prefer to avoid case sensitivity whenever possible in computer
handled data.
Received on Monday, 17 October 2011 15:45:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:48 GMT