#266, was: Case sensitivity of Transfer-Codings

Julian Reschke <julian.reschke@gmx.de> Tue, 31 January 2012 21:06 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 4485C21F865E for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 31 Jan 2012 13:06:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.1
X-Spam-Status: No, score=-8.1 tagged_above=-999 required=5 tests=[AWL=2.499, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id MTvm7rS8Opr3 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 31 Jan 2012 13:06:33 -0800 (PST)
Received: from frink.w3.org (frink.w3.org []) by ietfa.amsl.com (Postfix) with ESMTP id B4ECD21F865B for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 31 Jan 2012 13:06:33 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1RsKuA-0007Wz-JX for ietf-http-wg-dist@listhub.w3.org; Tue, 31 Jan 2012 21:06:18 +0000
Received: from lisa.w3.org ([]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <julian.reschke@gmx.de>) id 1RsKu0-0007Vw-2z for ietf-http-wg@listhub.w3.org; Tue, 31 Jan 2012 21:06:08 +0000
Received: from mailout-de.gmx.net ([]) by lisa.w3.org with smtp (Exim 4.72) (envelope-from <julian.reschke@gmx.de>) id 1RsKtx-0001mD-V9 for ietf-http-wg@w3.org; Tue, 31 Jan 2012 21:06:07 +0000
Received: (qmail invoked by alias); 31 Jan 2012 21:05:39 -0000
Received: from mail.greenbytes.de (EHLO []) [] by mail.gmx.net (mp033) with SMTP; 31 Jan 2012 22:05:39 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX198GT0fHtJ8ichCm0lsIepfqG1LxvYF6fV3iZbGI/ i/3M6x1Uma3dfP
Message-ID: <4F2857A2.5020805@gmx.de>
Date: Tue, 31 Jan 2012 22:05:38 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
CC: Dave Bordoley <bordoley@gmail.com>, ietf-http-wg@w3.org
References: <CAL4Fp5pT3WvYP3a-RJ7oxM00U-JZ2dypVUwC7JdpDD1kBSj9_w@mail.gmail.com> <9atei71svotg4cqkm3h59i83cgeg0m6vc5@hive.bjoern.hoehrmann.de>
In-Reply-To: <9atei71svotg4cqkm3h59i83cgeg0m6vc5@hive.bjoern.hoehrmann.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Received-SPF: pass client-ip=; envelope-from=julian.reschke@gmx.de; helo=mailout-de.gmx.net
X-W3C-Hub-Spam-Status: No, score=-1.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1RsKtx-0001mD-V9 ae5b4e2a5a594017f2a5df990d5bc264
X-Original-To: ietf-http-wg@w3.org
Subject: #266, was: Case sensitivity of Transfer-Codings
Archived-At: <http://www.w3.org/mid/4F2857A2.5020805@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/12274
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Resent-Message-Id: <E1RsKuA-0007Wz-JX@frink.w3.org>
Resent-Date: Tue, 31 Jan 2012 21:06:18 +0000

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