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

Re: #231: Considerations for new headers

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 13 Oct 2011 19:52:55 +0200
Message-ID: <4E972577.4080007@gmx.de>
To: Mark Nottingham <mnot@mnot.net>
CC: httpbis Group <ietf-http-wg@w3.org>
On 2011-10-10 10:26, Julian Reschke wrote:
> ...
> Also, we probably should have a single place that defines the "param"
> ABNF construct, like
>
> param = token OWS "=" OWS ( token / quoted-string )
>
> or maybe
>
> param = token OWS [ "=" OWS ( token / quoted-string ) ]
>
> and then clarify that predefined params never ever should parse
> different from extension parameters; for instance, they should always
> allow both notations.
>
> See also <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/307> and
> <http://trac.tools.ietf.org/wg/httpbis/trac/wiki/HeaderFieldTypes>.
> ...

Proposal:

"Many header fields use a format including named parameters (for 
instance, Content-Type). Parameter values should always allow both 
unquoted (token) and quoted (quoted-string) values:"

If we later get around to defining concrete ABNF building blocks, we can 
still rephrase this...

Best regards, Julian
Received on Thursday, 13 October 2011 17:53:25 GMT

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