Changeset 2178
- Timestamp:
- 06/02/13 09:10:24 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2177 r2178 449 449 } 450 450 @bottom-center { 451 content: "Expires August 5, 2013";451 content: "Expires August 10, 2013"; 452 452 } 453 453 @bottom-right { … … 491 491 <meta name="dct.creator" content="Reschke, J. F."> 492 492 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 493 <meta name="dct.issued" scheme="ISO8601" content="2013-02-0 1">493 <meta name="dct.issued" scheme="ISO8601" content="2013-02-06"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 520 520 <tr> 521 521 <td class="left">Intended status: Standards Track</td> 522 <td class="right">February 1, 2013</td>522 <td class="right">February 6, 2013</td> 523 523 </tr> 524 524 <tr> 525 <td class="left">Expires: August 5, 2013</td>525 <td class="left">Expires: August 10, 2013</td> 526 526 <td class="right"></td> 527 527 </tr> … … 551 551 in progress”. 552 552 </p> 553 <p>This Internet-Draft will expire on August 5, 2013.</p>553 <p>This Internet-Draft will expire on August 10, 2013.</p> 554 554 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 555 555 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1725 1725 <a href="#asterisk-form" class="smpl">asterisk-form</a> = "*" 1726 1726 </pre><div id="origin-form"> 1727 <p id="rfc.section.5.3.p.3"><span id="rfc.iref.o.3"></span> The most common form of request-target is the origin-form. When making a request directly to an origin server, other than 1728 a CONNECT or server-wide OPTIONS request (as detailed below), a client <em class="bcp14">MUST</em> send only the absolute path and query components of the target URI as the request-target. If the target URI's path component 1729 is empty, then the client <em class="bcp14">MUST</em> send "/" as the path within the origin-form of request-target. A <a href="#header.host" class="smpl">Host</a> header field is also sent, as defined in <a href="#header.host" id="rfc.xref.header.host.1" title="Host">Section 5.4</a>, containing the target URI's authority component (excluding any userinfo). 1727 <p id="rfc.section.5.3.p.3"><span id="rfc.iref.o.3"></span> <b>origin-form</b> 1730 1728 </p> 1731 1729 </div> 1732 <p id="rfc.section.5.3.p.4">For example, a client wishing to retrieve a representation of the resource identified as</p> 1730 <p id="rfc.section.5.3.p.4">The most common form of request-target is the <dfn>origin-form</dfn>. When making a request directly to an origin server, other than a CONNECT or server-wide OPTIONS request (as detailed below), 1731 a client <em class="bcp14">MUST</em> send only the absolute path and query components of the target URI as the request-target. If the target URI's path component 1732 is empty, then the client <em class="bcp14">MUST</em> send "/" as the path within the origin-form of request-target. A <a href="#header.host" class="smpl">Host</a> header field is also sent, as defined in <a href="#header.host" id="rfc.xref.header.host.1" title="Host">Section 5.4</a>, containing the target URI's authority component (excluding any userinfo). 1733 </p> 1734 <p id="rfc.section.5.3.p.5">For example, a client wishing to retrieve a representation of the resource identified as</p> 1733 1735 <div id="rfc.figure.u.38"></div><pre class="text">http://www.example.org/where?q=now 1734 </pre><p id="rfc.section.5.3.p. 6">directly from the origin server would open (or reuse) a TCP connection to port 80 of the host "www.example.org" and send the1736 </pre><p id="rfc.section.5.3.p.7">directly from the origin server would open (or reuse) a TCP connection to port 80 of the host "www.example.org" and send the 1735 1737 lines: 1736 1738 </p> 1737 1739 <div id="rfc.figure.u.39"></div><pre class="text2">GET /where?q=now HTTP/1.1 1738 1740 Host: www.example.org 1739 </pre><p id="rfc.section.5.3.p. 8">followed by the remainder of the request message.</p>1741 </pre><p id="rfc.section.5.3.p.9">followed by the remainder of the request message.</p> 1740 1742 <div id="absolute-form"> 1741 <p id="rfc.section.5.3.p.9"><span id="rfc.iref.a.2"></span> When making a request to a proxy, other than a CONNECT or server-wide OPTIONS request (as detailed below), a client <em class="bcp14">MUST</em> send the target URI in absolute-form as the request-target. The proxy is requested to either service that request from a valid 1742 cache, if possible, or make the same request on the client's behalf to either the next inbound proxy server or directly to 1743 the origin server indicated by the request-target. Requirements on such "forwarding" of messages are defined in <a href="#message.forwarding" title="Message Forwarding">Section 5.7</a>. 1743 <p id="rfc.section.5.3.p.10"><span id="rfc.iref.a.2"></span> <b>absolute-form</b> 1744 1744 </p> 1745 1745 </div> 1746 <p id="rfc.section.5.3.p.10">An example absolute-form of request-line would be:</p> 1746 <p id="rfc.section.5.3.p.11">When making a request to a proxy, other than a CONNECT or server-wide OPTIONS request (as detailed below), a client <em class="bcp14">MUST</em> send the target URI in <dfn>absolute-form</dfn> as the request-target. The proxy is requested to either service that request from a valid cache, if possible, or make the 1747 same request on the client's behalf to either the next inbound proxy server or directly to the origin server indicated by 1748 the request-target. Requirements on such "forwarding" of messages are defined in <a href="#message.forwarding" title="Message Forwarding">Section 5.7</a>. 1749 </p> 1750 <p id="rfc.section.5.3.p.12">An example absolute-form of request-line would be:</p> 1747 1751 <div id="rfc.figure.u.40"></div><pre class="text2">GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1 1748 </pre><p id="rfc.section.5.3.p.1 2">To allow for transition to the absolute-form for all requests in some future version of HTTP, HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absolute-form in requests, even though HTTP/1.1 clients will only send them in requests to proxies.1752 </pre><p id="rfc.section.5.3.p.14">To allow for transition to the absolute-form for all requests in some future version of HTTP, HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absolute-form in requests, even though HTTP/1.1 clients will only send them in requests to proxies. 1749 1753 </p> 1750 1754 <div id="authority-form"> 1751 <p id="rfc.section.5.3.p.1 3"><span id="rfc.iref.a.3"></span> The authority-form of request-target is only used for CONNECT requests (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 4.3.6</a> of <a href="#Part2" id="rfc.xref.Part2.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). When making a CONNECT request to establish a tunnel through one or more proxies, a client <em class="bcp14">MUST</em> send only the target URI's authority component (excluding any userinfo) as the request-target. For example,1755 <p id="rfc.section.5.3.p.15"><span id="rfc.iref.a.3"></span> <b>authority-form</b> 1752 1756 </p> 1753 1757 </div> 1758 <p id="rfc.section.5.3.p.16">The <dfn>authority-form</dfn> of request-target is only used for CONNECT requests (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 4.3.6</a> of <a href="#Part2" id="rfc.xref.Part2.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). When making a CONNECT request to establish a tunnel through one or more proxies, a client <em class="bcp14">MUST</em> send only the target URI's authority component (excluding any userinfo) as the request-target. For example, 1759 </p> 1754 1760 <div id="rfc.figure.u.41"></div><pre class="text2">CONNECT www.example.com:80 HTTP/1.1 1755 1761 </pre><div id="asterisk-form"> 1756 <p id="rfc.section.5.3.p.15"><span id="rfc.iref.a.4"></span> The asterisk-form of request-target is only used for a server-wide OPTIONS request (<a href="p2-semantics.html#OPTIONS" title="OPTIONS">Section 4.3.7</a> of <a href="#Part2" id="rfc.xref.Part2.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). When a client wishes to request OPTIONS for the server as a whole, as opposed to a specific named resource of that server, 1757 the client <em class="bcp14">MUST</em> send only "*" (%x2A) as the request-target. For example, 1762 <p id="rfc.section.5.3.p.18"><span id="rfc.iref.a.4"></span> <b>asterisk-form</b> 1758 1763 </p> 1759 1764 </div> 1765 <p id="rfc.section.5.3.p.19">The <dfn>asterisk-form</dfn> of request-target is only used for a server-wide OPTIONS request (<a href="p2-semantics.html#OPTIONS" title="OPTIONS">Section 4.3.7</a> of <a href="#Part2" id="rfc.xref.Part2.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). When a client wishes to request OPTIONS for the server as a whole, as opposed to a specific named resource of that server, 1766 the client <em class="bcp14">MUST</em> send only "*" (%x2A) as the request-target. For example, 1767 </p> 1760 1768 <div id="rfc.figure.u.42"></div><pre class="text2">OPTIONS * HTTP/1.1 1761 </pre><p id="rfc.section.5.3.p. 17">If a proxy receives an OPTIONS request with an absolute-form of request-target in which the URI has an empty path and no query1769 </pre><p id="rfc.section.5.3.p.21">If a proxy receives an OPTIONS request with an absolute-form of request-target in which the URI has an empty path and no query 1762 1770 component, then the last proxy on the request chain <em class="bcp14">MUST</em> send a request-target of "*" when it forwards the request to the indicated origin server. 1763 1771 </p> -
draft-ietf-httpbis/latest/p1-messaging.xml
r2177 r2178 2236 2236 </artwork></figure> 2237 2237 <t anchor="origin-form"><iref item="origin-form (of request-target)"/> 2238 The most common form of request-target is the origin-form. 2238 <x:h>origin-form</x:h> 2239 </t> 2240 <t> 2241 The most common form of request-target is the <x:dfn>origin-form</x:dfn>. 2239 2242 When making a request directly to an origin server, other than a CONNECT 2240 2243 or server-wide OPTIONS request (as detailed below), … … 2266 2269 </t> 2267 2270 <t anchor="absolute-form"><iref item="absolute-form (of request-target)"/> 2271 <x:h>absolute-form</x:h> 2272 </t> 2273 <t> 2268 2274 When making a request to a proxy, other than a CONNECT or server-wide 2269 2275 OPTIONS request (as detailed below), a client &MUST; send the target URI 2270 in absolute-formas the request-target.2276 in <x:dfn>absolute-form</x:dfn> as the request-target. 2271 2277 The proxy is requested to either service that request from a valid cache, 2272 2278 if possible, or make the same request on the client's behalf to either … … 2288 2294 </t> 2289 2295 <t anchor="authority-form"><iref item="authority-form (of request-target)"/> 2290 The authority-form of request-target is only used for CONNECT requests 2296 <x:h>authority-form</x:h> 2297 </t> 2298 <t> 2299 The <x:dfn>authority-form</x:dfn> of request-target is only used for CONNECT requests 2291 2300 (&CONNECT;). When making a CONNECT request to establish a tunnel through 2292 2301 one or more proxies, a client &MUST; send only the target URI's … … 2298 2307 </artwork></figure> 2299 2308 <t anchor="asterisk-form"><iref item="asterisk-form (of request-target)"/> 2300 The asterisk-form of request-target is only used for a server-wide 2309 <x:h>asterisk-form</x:h> 2310 </t> 2311 <t> 2312 The <x:dfn>asterisk-form</x:dfn> of request-target is only used for a server-wide 2301 2313 OPTIONS request (&OPTIONS;). When a client wishes to request OPTIONS 2302 2314 for the server as a whole, as opposed to a specific named resource of
Note: See TracChangeset
for help on using the changeset viewer.