W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1996

Re: HTTP 1.1 spec (page 15)

From: Koen Holtman <koen@win.tue.nl>
Date: Wed, 11 Dec 1996 22:14:17 +0100 (MET)
Message-Id: <199612112114.WAA19675@wsooti08.win.tue.nl>
To: "Roy T. Fielding" <fielding@liege.ICS.UCI.EDU>
Cc: Ulrich.Windl@rz.uni-regensburg.de, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Roy T. Fielding:
>
>Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> writes:
>> I wonder what the specification says about ``\)'' within a comment and
>> about ``\"'' within a quoted-string. To my interpretation of the specs
>> the character will be "quoted" but according to the grammar will
>> terminate the element anyhow.
>
>Hmmm, that's odd -- it was supposed to say
>
>    comment        = "(" *( ctext | quoted-pair | comment ) ")"
>
>    quoted-string  = ( <"> *( qdtext | quoted-pair ) <"> )
>
>I guess that should be put on the errata list.

Gack!  HTTP/1.0 says:

|   A string of text is parsed as a single word if it is quoted using
|   double-quote marks.
|
|       quoted-string  = ( <"> *(qdtext) <"> )
|
|       qdtext         = <any CHAR except <"> and CTLs,
|                        but including LWS>
|
|   Single-character quoting using the backslash ("\") character is not
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
|   permitted in HTTP/1.0.
    ^^^^^^^^^^^^^^^^^^^^^^

And I guess that most depoyed header parsers conform to this.  You would get
subtle but ugly incompatibility problems if you introduce single-character
quoting in 1.1.  In my opinion, we can only change the parsing of quoted
strings if we also increase the major version number.  The 1.1 grammar is
fine, the text is in error.

>.....Roy

Koen.
Received on Wednesday, 11 December 1996 13:23:16 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:32:19 EDT