I was looking at the HTML version of the HTTP standard on the W3C web site today. Apparently there’s a bug in their text-to-HTML conversion program, causing some words to lose their initial letters. Which led to this:
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.
Call me juvenile, but I laughed for a while when I read the first part of the second sentence…
Post Revisions:
There are no revisions for this post.
This is not just the W3C page, this is real. The entire paragraph is listed as an RFC 2617 errata.
10/16/2008 @ 4:56 pm
(And not just RFC2616, also RFC2617!)
10/16/2008 @ 4:57 pm
Wow, that’s awesome.
10/16/2008 @ 7:47 pm