Changeset 1968 for draft-ietf-httpbis

Timestamp:

03/11/12 13:53:18 (10 years ago)

Author:

julian.reschke@…

Message:

insert paragraph break

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

@@ -1128 +1128 @@
       <p id="rfc.section.3.1.p.1">An HTTP message can either be a request from client to server or a response from server to client. Syntactically, the two
          types of message 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 (<a href="#message.body" title="Message Body">Section&nbsp;3.3</a>). In theory, a client could receive requests and a server could receive responses, distinguishing them by their different
-         start-line formats, but in practice servers are implemented to only expect a request (a response is interpreted as an unknown
-         or invalid request method) and clients are implemented to only expect a response.
+         and in the algorithm for determining the length of the message body (<a href="#message.body" title="Message Body">Section&nbsp;3.3</a>).
+      </p>
+      <p id="rfc.section.3.1.p.2">In theory, a client could receive requests and a server could receive responses, distinguishing them by their different start-line
+         formats, but in practice servers are implemented to only expect a request (a response is interpreted as an unknown or invalid
+         request method) and clients are implemented to only expect a response.
       </p>
       <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.27"></span>  <a href="#http.message" class="smpl">start-line</a>     = <a href="#request.line" class="smpl">request-line</a> / <a href="#status.line" class="smpl">status-line</a>
-</pre><p id="rfc.section.3.1.p.3">A sender <em class="bcp14">MUST NOT</em> send whitespace between the start-line and the first header field. The presence of such whitespace in a request might be an
+</pre><p id="rfc.section.3.1.p.4">A sender <em class="bcp14">MUST NOT</em> send whitespace between the start-line and the first header field. The presence of such whitespace in a request might be an
          attempt to trick a server into ignoring that field or processing the line after it as a new request, either of which might
          result in a security vulnerability if other implementations within the request chain interpret the same message differently.

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

@@ -1025 +1025 @@
    or a status-line (for responses), and in the algorithm for determining
    the length of the message body (<xref target="message.body"/>).
+</t>
+<t>
    In theory, a client could receive requests and a server could receive
    responses, distinguishing them by their different start-line formats,