W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1999

more errata in RFC 2616

From: Roy T. Fielding <fielding@kiwi.ics.uci.edu>
Date: Tue, 03 Aug 1999 18:42:07 -0700
To: http-wg@hplb.hpl.hp.com
Message-ID: <9908031842.aa16159@paris.ics.uci.edu>
Some of the editorial notes got left in the text version.  That's what
all the 

   jg639 jg640 jg641 jg642 jg643 jg644 jg645 jg646 jg647

notes mean.

Also, this gem comes from Tony Finch:

------- Forwarded Message

Message-ID: <14245.33299.84271.563615@chiark.greenend.org.uk>
Date: Mon, 2 Aug 1999 12:33:39 +0100 (BST)
From: Tony Finch <dot@dotat.at>
Subject: RFC 2616

It looks like some characters are missing in section 4.4 paragraph 4:

   4.If the message uses the media type "multipart/byteranges", and the
     ransfer-length is not otherwise specified, then this self-
     elimiting media type defines the transfer-length. This media type
     UST NOT be used unless the sender knows that the recipient can arse
     it; the presence in a request of a Range header with ultiple byte-
     range specifiers from a 1.1 client implies that the lient can parse
     multipart/byteranges responses.

I particularly like "...MUST NOT be used unless the recipient can arse
it".

Tony.

------- End of Forwarded Message
Received on Wednesday, 4 August 1999 02:44:53 EDT

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