Link: http://trac.tools.ietf.org/wg/httpbis/trac/ticket/4
Origin: http://lists.w3.org/Archives/Public/ietf-http-wg-old/1999MayAug/0102.html
Component: p1-messaging
In the discussion of how to determine the message length [section 4.4], the fourth possibility somehow lost a number of characters. The spec says:
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.
It should read:
4.If the message uses the media type "multipart/byteranges", and the transfer-length is not otherwise specified, then this self- delimiting media type defines the transfer-length. This media type MUST NOT be used unless the sender knows that the recipient can parse it; the presence in a request of a Range header with multiple byte- range specifiers from a 1.1 client implies that the client can parse multipart/byteranges responses.
Fixed in [71]