Changeset 2262 for draft-ietf-httpbis/latest

Timestamp:

19/05/13 23:26:48 (10 years ago)

Author:

fielding@…

Message:

(editorial) address lame complaints

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (1 diff)
• p1-messaging.xml (modified) (1 diff)

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

@@ -1516 +1516 @@
       </p>
       <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a id="message.robustness" href="#message.robustness">Message Parsing Robustness</a></h2>
-      <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
-         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
+      <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 workaround for some early 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
          the user agent <em class="bcp14">MUST</em> count the terminating CRLF octets as part of the message body length.
       </p>

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

@@ -1833 +1833 @@
 <t>
    Older HTTP/1.0 user agent implementations might send an extra CRLF
-   after a POST request as a lame workaround for some early server
+   after a POST request as a workaround for some early server
    applications that failed to read message body content that was
    not terminated by a line-ending. An HTTP/1.1 user agent &MUST-NOT;