Ignore:
Timestamp:
Dec 29, 2012, 2:14:11 AM (7 years ago)
Author:
fielding@…
Message:

(editorial) rephrasing to better target the subject of requirements

File:
1 edited

Legend:

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

    r2053 r2066  
    449449  }
    450450  @bottom-center {
    451        content: "Expires June 19, 2013";
     451       content: "Expires July 2, 2013";
    452452  }
    453453  @bottom-right {
     
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2012-12-16">
     493      <meta name="dct.issued" scheme="ISO8601" content="2012-12-29">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    520520            <tr>
    521521               <td class="left">Intended status: Standards Track</td>
    522                <td class="right">December 16, 2012</td>
     522               <td class="right">December 29, 2012</td>
    523523            </tr>
    524524            <tr>
    525                <td class="left">Expires: June 19, 2013</td>
     525               <td class="left">Expires: July 2, 2013</td>
    526526               <td class="right"></td>
    527527            </tr>
     
    551551         in progress”.
    552552      </p>
    553       <p>This Internet-Draft will expire on June 19, 2013.</p>
     553      <p>This Internet-Draft will expire on July 2, 2013.</p>
    554554      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    555555      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    14781478         entire request before processing.
    14791479      </p>
    1480       <p id="rfc.section.3.3.3.p.6">A client that sends a request containing a message body <em class="bcp14">MUST</em> include a valid <a href="#header.content-length" class="smpl">Content-Length</a> header field if it does not know the server will handle HTTP/1.1 (or later) requests; such knowledge can be in the form of
     1480      <p id="rfc.section.3.3.3.p.6">A user agent that sends a request containing a message body <em class="bcp14">MUST</em> send a valid <a href="#header.content-length" class="smpl">Content-Length</a> header field if it does not know the server will handle HTTP/1.1 (or later) requests; such knowledge can be in the form of
    14811481         specific user configuration or by remembering the version of a prior received response.
    14821482      </p>
     
    15031503      <p id="rfc.section.3.5.p.1">Older HTTP/1.0 user agent implementations might send an extra CRLF after a POST request as a lame workaround for some early
    15041504         server applications that failed to read message body content that was not terminated by a line-ending. An HTTP/1.1 user agent <em class="bcp14">MUST NOT</em> preface or follow a request with an extra CRLF. If terminating the request message body with a line-ending is desired, then
    1505          the user agent <em class="bcp14">MUST</em> include the terminating CRLF octets as part of the message body length.
     1505         the user agent <em class="bcp14">MUST</em> count the terminating CRLF octets as part of the message body length.
    15061506      </p>
    15071507      <p id="rfc.section.3.5.p.2">In the interest of robustness, servers <em class="bcp14">SHOULD</em> ignore at least one empty line received where a request-line is expected. In other words, if a server is reading the protocol
Note: See TracChangeset for help on using the changeset viewer.