Ignore:
Timestamp:
Aug 12, 2009, 6:21:32 PM (10 years ago)
Author:
fielding@…
Message:

editorial: wordsmith description of messages

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r676 r677  
    856856      <div id="rfc.iref.r.2"></div>
    857857      <p id="rfc.section.2.1.p.5">A client sends an HTTP request to the server in the form of a request message (<a href="#request" title="Request">Section&nbsp;4</a>), beginning with a method, URI, and protocol version, followed by MIME-like header fields containing request modifiers, client
    858          information, and payload metadata, an empty line, and finally the payload body (if any). The server response (<a href="#response" title="Response">Section&nbsp;5</a>) begins with a status line, including the protocol version, a success or error code, and textual reason phrase, followed
    859          by MIME-like header fields containing server information, resource metadata, payload metadata, an empty line, and finally
    860          the payload body (if any).
    861       </p>
    862       <p id="rfc.section.2.1.p.6">The following example illustrates a typical message exchange for a GET request on the URI "http://www.example.com/hello.txt":</p>
     858         information, and payload metadata, an empty line to indicate the end of the header section, and finally the payload body (if
     859         any).
     860      </p>
     861      <p id="rfc.section.2.1.p.6">A server responds to the client's request by sending an HTTP response message (<a href="#response" title="Response">Section&nbsp;5</a>), beginning with a status line that includes the protocol version, a success or error code, and textual reason phrase, followed
     862         by MIME-like header fields containing server information, resource metadata, and payload metadata, an empty line to indicate
     863         the end of the header section, and finally the payload body (if any).
     864      </p>
     865      <p id="rfc.section.2.1.p.7">The following example illustrates a typical message exchange for a GET request on the URI "http://www.example.com/hello.txt":</p>
    863866      <div id="rfc.figure.u.13"></div>
    864867      <p>client request:</p><pre class="text2">GET /hello.txt HTTP/1.1
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r676 r677  
    550550   protocol version, followed by MIME-like header fields containing
    551551   request modifiers, client information, and payload metadata, an empty
    552    line, and finally the payload body (if any).
    553    The server response (<xref target="response"/>) begins with a status line,
    554    including the protocol version, a success or error code, and textual
     552   line to indicate the end of the header section, and finally the payload
     553   body (if any).
     554</t>
     555<t>
     556   A server responds to the client's request by sending an HTTP response
     557   message (<xref target="response"/>), beginning with a status line that
     558   includes the protocol version, a success or error code, and textual
    555559   reason phrase, followed by MIME-like header fields containing server
    556    information, resource metadata, payload metadata, an empty line, and
    557    finally the payload body (if any).
     560   information, resource metadata, and payload metadata, an empty line to
     561   indicate the end of the header section, and finally the payload body (if any).
    558562</t>
    559563<t>
Note: See TracChangeset for help on using the changeset viewer.