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

Re: new issue: mismatch between RFC2616 and RFC4234 CHAR definition

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 24 Jan 2008 15:14:24 +0100
Message-ID: <47989D40.30508@gmx.de>
To: lists@ingostruck.de
CC: HTTP Working Group <ietf-http-wg@w3.org>

lists@ingostruck.de wrote:
> On Thursday 24 January 2008, Julian Reschke wrote:
>> I just realized that the "CHAR" core rules in RFC2616 and RFC4234
>> differ, in that RFC2616 includes NUL:
>>      CHAR           = <any US-ASCII character (octets 0 - 127)>
>>
>>      token          = 1*<any CHAR except CTLs or separators>
>> Are these productions really intended to allow NUL?
> The "token" production explicitly disallows NUL ("except CTLs").

Indeed. Thanks.

> As for quoted-string: quoting is meant to enable the usage 
> of *any* CHAR within the quotes or am I wrong?

Not convinced. If the intent was to allow NUL in quoted strings (after 
unquoting), why isn't it allowed in qdtext in the first place?

     quoted-string  = ( <"> *(qdtext | quoted-pair ) <"> )
     qdtext         = <any TEXT except <">>
     TEXT           = <any OCTET except CTLs,
                      but including LWS>

BR, Julian
Received on Thursday, 24 January 2008 14:14:42 GMT

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