Changeset 1480
- Timestamp:
- 26/11/11 18:07:07 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1479 r1480 1475 1475 <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a> <a id="request-target-types" href="#request-target-types">Types of Request Target</a></h2> 1476 1476 <p id="rfc.section.4.1.p.1">The four options for request-target are dependent on the nature of the request.</p> 1477 <p id="rfc.section.4.1.p.2"><span id="rfc.iref.a.2"></span> The asterisk "*" form of request-target, which <em class="bcp14">MUST NOT</em> be used with any request method other than OPTIONS, means that the request applies to the server as a whole (the listening 1478 process) rather than to a specific named resource at that server. For example, 1479 </p> 1477 <div id="asterix-form"> 1478 <p id="rfc.section.4.1.p.2"><span id="rfc.iref.a.2"></span> The asterisk "*" form of request-target, which <em class="bcp14">MUST NOT</em> be used with any request method other than OPTIONS, means that the request applies to the server as a whole (the listening 1479 process) rather than to a specific named resource at that server. For example, 1480 </p> 1481 </div> 1480 1482 <div id="rfc.figure.u.34"></div><pre class="text2">OPTIONS * HTTP/1.1 1481 </pre><p id="rfc.section.4.1.p.4"><span id="rfc.iref.a.3"></span> The "absolute-URI" form is <em class="bcp14">REQUIRED</em> when the request is being made to a proxy. The proxy is requested to either forward the request or service it from a valid 1482 cache, and then 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 1483 loops, a proxy that forwards requests to other proxies <em class="bcp14">MUST</em> be able to recognize and exclude all of its own server names, including any aliases, local variations, and the numeric IP 1484 address. An example Request-Line would be: 1485 </p> 1483 </pre><div id="absolute-URI-form"> 1484 <p id="rfc.section.4.1.p.4"><span id="rfc.iref.a.3"></span> The "absolute-URI" form is <em class="bcp14">REQUIRED</em> when the request is being made to a proxy. The proxy is requested to either forward the request or service it from a valid 1485 cache, and then 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 1486 loops, a proxy that forwards requests to other proxies <em class="bcp14">MUST</em> be able to recognize and exclude all of its own server names, including any aliases, local variations, and the numeric IP 1487 address. An example Request-Line would be: 1488 </p> 1489 </div> 1486 1490 <div id="rfc.figure.u.35"></div><pre class="text2">GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1 1487 1491 </pre><p id="rfc.section.4.1.p.6">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. … … 1489 1493 <p id="rfc.section.4.1.p.7">If a proxy receives a host name that is not a fully qualified domain name, it <em class="bcp14">MAY</em> add its domain to the host name it received. If a proxy receives a fully qualified domain name, the proxy <em class="bcp14">MUST NOT</em> change the host name. 1490 1494 </p> 1491 <p id="rfc.section.4.1.p.8"><span id="rfc.iref.a.4"></span> The "authority form" is only used by the CONNECT request method (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 6.9</a> of <a href="#Part2" id="rfc.xref.Part2.9"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). 1492 </p> 1493 <p id="rfc.section.4.1.p.9"><span id="rfc.iref.o.3"></span> The most common form of request-target is that used when making a request to an origin server ("origin form"). In this case, 1494 the absolute path and query components of the URI <em class="bcp14">MUST</em> be transmitted as the request-target, and the authority component <em class="bcp14">MUST</em> be transmitted in a Host header field. For example, a client wishing to retrieve a representation of the resource, as identified 1495 above, directly from the origin server would open (or reuse) a TCP connection to port 80 of the host "www.example.org" and 1496 send the lines: 1497 </p> 1495 <div id="authority-form"> 1496 <p id="rfc.section.4.1.p.8"><span id="rfc.iref.a.4"></span> The "authority form" is only used by the CONNECT request method (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 6.9</a> of <a href="#Part2" id="rfc.xref.Part2.9"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). 1497 </p> 1498 </div> 1499 <div id="origin-form"> 1500 <p id="rfc.section.4.1.p.9"><span id="rfc.iref.o.3"></span> The most common form of request-target is that used when making a request to an origin server ("origin form"). In this case, 1501 the absolute path and query components of the URI <em class="bcp14">MUST</em> be transmitted as the request-target, and the authority component <em class="bcp14">MUST</em> be transmitted in a Host header field. For example, a client wishing to retrieve a representation of the resource, as identified 1502 above, directly from the origin server would open (or reuse) a TCP connection to port 80 of the host "www.example.org" and 1503 send the lines: 1504 </p> 1505 </div> 1498 1506 <div id="rfc.figure.u.36"></div><pre class="text2">GET /pub/WWW/TheProject.html HTTP/1.1 1499 1507 Host: www.example.org … … 1550 1558 </p> 1551 1559 <p id="rfc.section.4.3.p.2">If the request-target is an absolute-URI, then the effective request URI is the request-target.</p> 1552 <p id="rfc.section.4.3.p.3">If the request-target uses the path-absoluteform or the asterisk form, and the Host header field is present, then the effective1560 <p id="rfc.section.4.3.p.3">If the request-target uses the origin form or the asterisk form, and the Host header field is present, then the effective 1553 1561 request URI is constructed by concatenating 1554 1562 </p> … … 1563 1571 <li>the request-target obtained from the Request-Line, unless the request-target is just the asterisk "*".</li> 1564 1572 </ul> 1565 <p id="rfc.section.4.3.p.5">If the request-target uses the path-absolute form or the asterisk form, and the Host header field is not present, then the1566 effectiverequest URI is undefined.1573 <p id="rfc.section.4.3.p.5">If the request-target uses the origin form or the asterisk form, and the Host header field is not present, then the effective 1574 request URI is undefined. 1567 1575 </p> 1568 1576 <p id="rfc.section.4.3.p.6">Otherwise, when request-target uses the authority form, the effective request URI is undefined.</p> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1479 r1480 1805 1805 request. 1806 1806 </t> 1807 <t ><iref item="asterisk form (of request-target)"/>1807 <t anchor="asterix-form"><iref item="asterisk form (of request-target)"/> 1808 1808 The asterisk "*" form of request-target, which &MUST-NOT; be used 1809 1809 with any request method other than OPTIONS, means that the request … … 1814 1814 OPTIONS * HTTP/1.1 1815 1815 </artwork></figure> 1816 <t ><iref item="absolute-URI form (of request-target)"/>1816 <t anchor="absolute-URI-form"><iref item="absolute-URI form (of request-target)"/> 1817 1817 The "absolute-URI" form is &REQUIRED; when the request is being made to a 1818 1818 proxy. The proxy is requested to either forward the request or service it … … 1840 1840 the host name. 1841 1841 </t> 1842 <t ><iref item="authority form (of request-target)"/>1842 <t anchor="authority-form"><iref item="authority form (of request-target)"/> 1843 1843 The "authority form" is only used by the CONNECT request method (&CONNECT;). 1844 1844 </t> 1845 <t ><iref item="origin form (of request-target)"/>1845 <t anchor="origin-form"><iref item="origin form (of request-target)"/> 1846 1846 The most common form of request-target is that used when making 1847 1847 a request to an origin server ("origin form"). … … 1960 1960 </t> 1961 1961 <t> 1962 If the request-target uses the path-absoluteform or the asterisk form,1962 If the request-target uses the origin form or the asterisk form, 1963 1963 and the Host header field is present, then the effective request URI is 1964 1964 constructed by concatenating … … 1985 1985 </t> 1986 1986 <t> 1987 If the request-target uses the path-absoluteform or the asterisk form,1987 If the request-target uses the origin form or the asterisk form, 1988 1988 and the Host header field is not present, then the effective request URI is 1989 1989 undefined.
Note: See TracChangeset
for help on using the changeset viewer.