Ignore:
Timestamp:
Nov 3, 2012, 6:53:18 AM (7 years ago)
Author:
julian.reschke@…
Message:

insert paragraph break

File:
1 edited

Legend:

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

    r1967 r1968  
    11281128      <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
    11291129         types of message differ only in the start-line, which is either a request-line (for requests) or a status-line (for responses),
    1130          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
    1131          start-line formats, but in practice servers are implemented to only expect a request (a response is interpreted as an unknown
    1132          or invalid request method) and clients are implemented to only expect a response.
     1130         and in the algorithm for determining the length of the message body (<a href="#message.body" title="Message Body">Section&nbsp;3.3</a>).
     1131      </p>
     1132      <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
     1133         formats, but in practice servers are implemented to only expect a request (a response is interpreted as an unknown or invalid
     1134         request method) and clients are implemented to only expect a response.
    11331135      </p>
    11341136      <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>
    1135 </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
     1137</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
    11361138         attempt to trick a server into ignoring that field or processing the line after it as a new request, either of which might
    11371139         result in a security vulnerability if other implementations within the request chain interpret the same message differently.
Note: See TracChangeset for help on using the changeset viewer.