Changeset 864


Ignore:
Timestamp:
Jul 21, 2010, 11:43:10 PM (9 years ago)
Author:
fielding@…
Message:

Fix references to old section on body length so that they
just point to the body section.

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r859 r864  
    10541054   differ only in the start-line, which is either a Request-Line (for requests)
    10551055   or a Status-Line (for responses), and in the algorithm for determining
    1056    the length of the message-body (<xref target="message.body.length"/>).
     1056   the length of the message-body (<xref target="message.body"/>).
    10571057   In theory, a client could receive requests and a server could receive
    10581058   responses, distinguishing them by their different start-line formats,
     
    12701270   &MAY; be of zero length.
    12711271</t>
    1272 <t anchor="message.body.length">
     1272<t>
    12731273   The length of the message-body is determined by one of the following
    12741274   (in order of precedence):
     
    19711971   is used, it &MUST; be the last transfer-coding applied to form the
    19721972   message-body. The "chunked" transfer-coding &MUST-NOT; be applied more
    1973    than once to a message-body. These rules allow the recipient to
    1974    determine the message-body length of the message (<xref target="message.body.length"/>).
     1973   than once to a message-body.
    19751974</t>
    19761975<t>
     
    19811980   has a different focus for an 8bit-clean transfer protocol. In HTTP,
    19821981   the only unsafe characteristic of message-bodies is the difficulty in
    1983    determining the exact body length (<xref target="message.body.length"/>), or the desire to
    1984    encrypt data over a shared transport.
     1982   determining the exact message body length (<xref target="message.body"/>),
     1983   or the desire to encrypt data over a shared transport.
    19851984</t>
    19861985<t>
     
    23482347   In order to remain persistent, all messages on the connection &MUST;
    23492348   have a self-defined message length (i.e., one not defined by closure
    2350    of the connection), as described in <xref target="message.body.length"/>.
     2349   of the connection), as described in <xref target="message.body"/>.
    23512350</t>
    23522351</section>
     
    29082907   length when no transfer-coding is being applied and the
    29092908   payload's body length can be determined prior to being transferred.
     2909   <xref target="message.body"/> describes how recipients determine the length
     2910   of a message-body.
    29102911</t>
    29112912<t>
    29122913   Any Content-Length greater than or equal to zero is a valid value.
    2913    <xref target="message.body.length"/> describes how to determine the length of a message-body
    2914    if a Content-Length is not given.
    2915 </t>
    2916 <t>
    2917    Note that the meaning of this field is significantly different from
     2914</t>
     2915<t>
     2916   Note that the use of this field in HTTP is significantly different from
    29182917   the corresponding definition in MIME, where it is an optional field
    29192918   used within the "message/external-body" content-type.
     
    48734872   transfer encoding that may not be self delimiting); it was important
    48744873   to straighten out exactly how message lengths are computed. (Sections
    4875    <xref target="transfer.codings" format="counter"/>, <xref target="message.body.length" format="counter"/>,
     4874   <xref target="transfer.codings" format="counter"/>, <xref target="message.body" format="counter"/>,
    48764875   <xref target="header.content-length" format="counter"/>,
    48774876   see also <xref target="Part5"/>)
     
    49304929  Remove reference to non-existent identity transfer-coding value tokens.
    49314930  (Sections <xref format="counter" target="transfer.codings"/> and
    4932   <xref format="counter" target="message.body.length"/>)
     4931  <xref format="counter" target="message.body"/>)
    49334932</t>
    49344933<t>
  • draft-ietf-httpbis/latest/p3-payload.xml

    r859 r864  
    2727  <!ENTITY header-vary              "<xref target='Part6' x:rel='#header.vary' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2828  <!ENTITY message-body             "<xref target='Part1' x:rel='#message.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    29   <!ENTITY message-length           "<xref target='Part1' x:rel='#message.body.length' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3029  <!ENTITY header-fields            "<xref target='Part1' x:rel='#header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3130  <!ENTITY multipart-byteranges     "<xref target='Part5' x:rel='#internet.media.type.multipart.byteranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
Note: See TracChangeset for help on using the changeset viewer.