Opened 12 years ago

Closed 12 years ago

Last modified 11 years ago

#4 closed editorial (fixed)

Message Length

Reported by: mnot@… Owned by:
Priority: Milestone: 01
Component: p1-messaging Severity:
Keywords: Cc:

Description

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.

Change History (4)

comment:1 Changed 12 years ago by fielding@…

  • Milestone set to 01
  • Resolution set to fixed
  • Status changed from new to closed
  • version set to 00

Fixed in [71]

comment:2 Changed 12 years ago by mnot@…

  • version changed from 00 to d00

comment:3 Changed 11 years ago by julian.reschke@…

  • Component set to p1-messaging

comment:4 Changed 11 years ago by julian.reschke@…

  • origin set to http://lists.w3.org/Archives/Public/ietf-http-wg-old/1999MayAug/0102.html
Note: See TracTickets for help on using tickets.