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

#266, was: Case sensitivity of Transfer-Codings

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 31 Jan 2012 22:05:38 +0100
Message-ID: <4F2857A2.5020805@gmx.de>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
CC: Dave Bordoley <bordoley@gmail.com>, ietf-http-wg@w3.org
On 2012-01-31 06:02, Bjoern Hoehrmann wrote:
> * Dave Bordoley wrote:
>> In version 18 of the draft spec it states that "All transfer-coding
>> values are case-insensitive." Its a little unclear whether this also
>> applies to the attribute/value pairs that make up a
>> transfer-parameter. In similar key/value pairs, attribute values tend
>> to be case insensitive while values are not. For instance, the spec
>> for media types states: "The type, subtype, and parameter attribute
>> names are case-insensitive.  Parameter values might or might not be
>> case-sensitive." It would be nice for the spec to state this
>> explicitly as well transfer-codings.
> (FWIW, I thought this would be already very clear and looked up the
> section Dave Bordoley was missing, but upon further inspection, I do
> agree that there should be some text to this effect, or this should
> be organized differently, like having a generic definition that says
> parameter names are case-insensitive, for values see the individual
> parameter definition.)

In theory.

Right now, header field definitions are really all stand-alone. We 
really should state the general principles in a single place (param name 
case-insensitive, value case-sensitive unless otherwise noted).

This seems to be a part of issue 266.

Best regards, Julian
Received on Tuesday, 31 January 2012 21:06:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:00 UTC