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

Re: TICKET 259: 'treat as invalid' not defined

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 13 Dec 2010 10:47:44 +0100
Message-ID: <4D05EBC0.6010501@gmx.de>
To: Adam Barth <ietf@adambarth.com>
CC: Mark Nottingham <mnot@mnot.net>, httpbis <ietf-http-wg@w3.org>
On 11.12.2010 23:46, Julian Reschke wrote:
> On 11.12.2010 20:42, Adam Barth wrote:
> ...
>>> Note that this step starts with an octet sequence obtained from the
>>> HTTP message, and results in a sequence of Unicode characters.
>>
>> Somewhere we want to say what character set we're using.
>
> Indeed. Will fix.
> ...

I moved that up to an earlier section (see also 
<http://trac.tools.ietf.org/wg/httpbis/trac/attachment/ticket/259/i259.2.diff>):

D.2.  Parsing for Disposition Type and Parameters

    Using the simplified grammar below:

      field-value = disp-type *( ";" param )
      disp-type   = token
      param       = token "=" value

    ...parse the octet sequence in the field value into a disp-type
    (disposition type) and a sequence of parameters (pairs of name
    (token) and value).

    Treat the result values as characters encoded using the ISO-8859-1
    character encoding ([ISO-8859-1]).

    Lower-case all disposition types and parameter names (note that these
    characters will all fall into the US-ASCII range by definition in the
    ABNF).

    If the field value does not conform to the grammar (such as when not
    exactly one disposition type is specified), ignore the whole header
    field.

(I think this better reflects how implementations will actually work; 
maybe the "treat-as-ISO" statement should even be moved to the top).

Best regards, Julian
Received on Monday, 13 December 2010 09:48:18 GMT

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