Ignore:
Timestamp:
Apr 2, 2010, 10:14:53 AM (9 years ago)
Author:
julian.reschke@…
Message:

improve example markup

File:
1 edited

Legend:

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

    r802 r803  
    13121312         apply to a resource. One example would be
    13131313      </p>
    1314       <div id="rfc.figure.u.35"></div><pre class="text">  OPTIONS * HTTP/1.1
     1314      <div id="rfc.figure.u.35"></div><pre class="text2">OPTIONS * HTTP/1.1
    13151315</pre><p id="rfc.section.4.1.2.p.5">The absolute-URI form is <em class="bcp14">REQUIRED</em> when the request is being made to a proxy. The proxy is requested to forward the request or service it from a valid cache,
    13161316         and return the response. Note that the proxy <em class="bcp14">MAY</em> forward the request on to another proxy or directly to the server specified by the absolute-URI. In order to avoid request
     
    13181318         Request-Line would be:
    13191319      </p>
    1320       <div id="rfc.figure.u.36"></div><pre class="text">  GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
     1320      <div id="rfc.figure.u.36"></div><pre class="text2">GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
    13211321</pre><p id="rfc.section.4.1.2.p.7">To allow for transition to absolute-URIs in all requests in future versions of HTTP, all HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absolute-URI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies.
    13221322      </p>
     
    13271327         server would create a TCP connection to port 80 of the host "www.example.org" and send the lines:
    13281328      </p>
    1329       <div id="rfc.figure.u.37"></div><pre class="text">  GET /pub/WWW/TheProject.html HTTP/1.1
    1330   Host: www.example.org
     1329      <div id="rfc.figure.u.37"></div><pre class="text2">GET /pub/WWW/TheProject.html HTTP/1.1
     1330Host: www.example.org
    13311331</pre><p id="rfc.section.4.1.2.p.11">followed by the remainder of the Request. Note that the absolute path cannot be empty; if none is present in the original
    13321332         URI, it <em class="bcp14">MUST</em> be given as "/" (the server root).
     
    13361336      </p>
    13371337      <div id="rfc.figure.u.38"></div>
    1338       <p>For example, the request</p><pre class="text">  OPTIONS http://www.example.org:8001 HTTP/1.1
     1338      <p>For example, the request</p><pre class="text2">OPTIONS http://www.example.org:8001 HTTP/1.1
    13391339</pre><div id="rfc.figure.u.39"></div>
    1340       <p>would be forwarded by the proxy as</p><pre class="text">  OPTIONS * HTTP/1.1
    1341   Host: www.example.org:8001
     1340      <p>would be forwarded by the proxy as</p><pre class="text2">OPTIONS * HTTP/1.1
     1341Host: www.example.org:8001
    13421342</pre>  <p>after connecting to port 8001 of host "www.example.org".</p>
    13431343      <p id="rfc.section.4.1.2.p.15">The request-target is transmitted in the format specified in <a href="#http.uri" title="http URI scheme">Section&nbsp;2.6.1</a>. If the request-target is percent-encoded (<a href="#RFC3986" id="rfc.xref.RFC3986.17"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>), the origin server <em class="bcp14">MUST</em> decode the request-target in order to properly interpret the request. Servers <em class="bcp14">SHOULD</em> respond to invalid request-targets with an appropriate status code.
     
    20282028         URL). For example, a request on the origin server for &lt;http://www.example.org/pub/WWW/&gt; would properly include:
    20292029      </p>
    2030       <div id="rfc.figure.u.63"></div><pre class="text">  GET /pub/WWW/ HTTP/1.1
    2031   Host: www.example.org
     2030      <div id="rfc.figure.u.63"></div><pre class="text2">GET /pub/WWW/ HTTP/1.1
     2031Host: www.example.org
    20322032</pre><p id="rfc.section.9.4.p.6">A client <em class="bcp14">MUST</em> include a Host header field in all HTTP/1.1 request messages. If the requested URI does not include an Internet host name
    20332033         for the service being requested, then the Host header field <em class="bcp14">MUST</em> be given with an empty value. An HTTP/1.1 proxy <em class="bcp14">MUST</em> ensure that any request message it forwards does contain an appropriate Host header field that identifies the service being
Note: See TracChangeset for help on using the changeset viewer.