Changeset 2262 for draft-ietf-httpbis/latest
- Timestamp:
- 19/05/13 23:26:48 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2261 r2262 1516 1516 </p> 1517 1517 <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a> <a id="message.robustness" href="#message.robustness">Message Parsing Robustness</a></h2> 1518 <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 early1519 serverapplications 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, then1518 <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 1519 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 1520 1520 the user agent <em class="bcp14">MUST</em> count the terminating CRLF octets as part of the message body length. 1521 1521 </p> -
draft-ietf-httpbis/latest/p1-messaging.xml
r2261 r2262 1833 1833 <t> 1834 1834 Older HTTP/1.0 user agent implementations might send an extra CRLF 1835 after a POST request as a lameworkaround for some early server1835 after a POST request as a workaround for some early server 1836 1836 applications that failed to read message body content that was 1837 1837 not terminated by a line-ending. An HTTP/1.1 user agent &MUST-NOT;
Note: See TracChangeset
for help on using the changeset viewer.