- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Thu, 24 Jan 2008 12:15:54 -0800
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
On Jan 24, 2008, at 5:54 AM, 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)> > > (<http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.2.2>) > > CHAR is only used in two places: > > token = 1*<any CHAR except CTLs or separators> > > and > > quoted-pair = "\" CHAR > > (same section). > > Are these productions really intended to allow NUL? No, and no one sends it, so just note the difference and use RFC4234. ....Roy
Received on Thursday, 24 January 2008 20:15:53 UTC