- 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>
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 UTC