RE: Uppercase/lowercase header field names from RUELLAN Herve on 2013-10-17 (ietf-http-wg@w3.org from October to December 2013)

From: RUELLAN Herve <Herve.Ruellan@crf.canon.fr>
Date: Thu, 17 Oct 2013 12:31:28 +0000
To: Fred Akalin <akalin@google.com>, Martin Thomson <martin.thomson@gmail.com>
CC: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <6C71876BDCCD01488E70A2399529D5E52F50E8D5@ADELE.crf.canon.fr>

From my understanding, we decided in Seattle that Header names would also be opaque bytes.

I made the changes accordingly in the HPack spec on github.

Hervé.

> -----Original Message-----
> From: Fred Akalin [mailto:akalin@google.com]
> Sent: mercredi 16 octobre 2013 02:21
> To: Martin Thomson
> Cc: HTTP Working Group
> Subject: Re: Uppercase/lowercase header field names
> 
> On Tue, Oct 15, 2013 at 5:15 PM, Martin Thomson
> <martin.thomson@gmail.com> wrote:
> 
> 
>  With the decision to have header compression treat header data as
>  opaque bytes, we're back to the old problem we never solved
> regarding
>  the requirement to downcase header field names.  In fact, it was
>  missing from -06 and no one noticed.
> 
> 
> 
> Just to clarify, we decided to treat header *values* as opaque bytes. Header
> names are still constrained to have only lowercase alpha characters (see 4.1.2
> in http://tools.ietf.org/html/draft-ietf-httpbis-header-compression-03).

Received on Thursday, 17 October 2013 12:31:58 UTC