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

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").

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

Regards

Ingo Struck