Changeset 864 for draft-ietf-httpbis

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:

• p1-messaging.xml (modified) (8 diffs)
• p3-payload.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -1054 +1054 @@
    differ only in the start-line, which is either a Request-Line (for requests)
    or a Status-Line (for responses), and in the algorithm for determining
-   the length of the message-body (<xref target="message.body.length"/>).
+   the length of the message-body (<xref target="message.body"/>).
    In theory, a client could receive requests and a server could receive
    responses, distinguishing them by their different start-line formats,
@@ -1270 +1270 @@
    &MAY; be of zero length.
 </t>
-<t anchor="message.body.length">
+<t>
    The length of the message-body is determined by one of the following
    (in order of precedence):
@@ -1971 +1971 @@
    is used, it &MUST; be the last transfer-coding applied to form the
    message-body. The "chunked" transfer-coding &MUST-NOT; be applied more
-   than once to a message-body. These rules allow the recipient to
-   determine the message-body length of the message (<xref target="message.body.length"/>).
+   than once to a message-body.
 </t>
 <t>
@@ -1981 +1980 @@
    has a different focus for an 8bit-clean transfer protocol. In HTTP,
    the only unsafe characteristic of message-bodies is the difficulty in
-   determining the exact body length (<xref target="message.body.length"/>), or the desire to
-   encrypt data over a shared transport.
+   determining the exact message body length (<xref target="message.body"/>),
+   or the desire to encrypt data over a shared transport.
 </t>
 <t>
@@ -2348 +2347 @@
    In order to remain persistent, all messages on the connection &MUST;
    have a self-defined message length (i.e., one not defined by closure
-   of the connection), as described in <xref target="message.body.length"/>.
+   of the connection), as described in <xref target="message.body"/>.
 </t>
 </section>
@@ -2908 +2907 @@
    length when no transfer-coding is being applied and the
    payload's body length can be determined prior to being transferred.
+   <xref target="message.body"/> describes how recipients determine the length
+   of a message-body.
 </t>
 <t>
    Any Content-Length greater than or equal to zero is a valid value.
-   <xref target="message.body.length"/> describes how to determine the length of a message-body
-   if a Content-Length is not given.
-</t>
-<t>
-   Note that the meaning of this field is significantly different from
+</t>
+<t>
+   Note that the use of this field in HTTP is significantly different from
    the corresponding definition in MIME, where it is an optional field
    used within the "message/external-body" content-type.
@@ -4873 +4872 @@
    transfer encoding that may not be self delimiting); it was important
    to straighten out exactly how message lengths are computed. (Sections
-   <xref target="transfer.codings" format="counter"/>, <xref target="message.body.length" format="counter"/>,
+   <xref target="transfer.codings" format="counter"/>, <xref target="message.body" format="counter"/>,
    <xref target="header.content-length" format="counter"/>,
    see also <xref target="Part5"/>)
@@ -4930 +4929 @@
   Remove reference to non-existent identity transfer-coding value tokens.
   (Sections <xref format="counter" target="transfer.codings"/> and
-  <xref format="counter" target="message.body.length"/>)
+  <xref format="counter" target="message.body"/>)
 </t>
 <t>

draft-ietf-httpbis/latest/p3-payload.xml

@@ -27 +27 @@
   <!ENTITY header-vary              "<xref target='Part6' x:rel='#header.vary' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY message-body             "<xref target='Part1' x:rel='#message.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
-  <!ENTITY message-length           "<xref target='Part1' x:rel='#message.body.length' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY header-fields            "<xref target='Part1' x:rel='#header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY multipart-byteranges     "<xref target='Part5' x:rel='#internet.media.type.multipart.byteranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">