Changeset 1833 for draft-ietf-httpbis/latest/p1-messaging.html
- Timestamp:
- 20/08/12 00:10:23 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1832 r1833 639 639 <li><a href="#rfc.section.5.4">5.4</a> <a href="#header.host">Host</a></li> 640 640 <li><a href="#rfc.section.5.5">5.5</a> <a href="#effective.request.uri">Effective Request URI</a></li> 641 <li><a href="#rfc.section.5.6">5.6</a> <a href="# intermediary.forwarding">IntermediaryForwarding</a><ul>641 <li><a href="#rfc.section.5.6">5.6</a> <a href="#message.forwarding">Message Forwarding</a><ul> 642 642 <li><a href="#rfc.section.5.6.1">5.6.1</a> <a href="#end-to-end.and.hop-by-hop.header-fields">End-to-end and Hop-by-hop Header Fields</a></li> 643 643 <li><a href="#rfc.section.5.6.2">5.6.2</a> <a href="#non-modifiable.header-fields">Non-modifiable Header Fields</a></li> … … 1700 1700 </p> 1701 1701 <p id="rfc.section.5.1.p.2">HTTP communication is initiated by a user agent for some purpose. The purpose is a combination of request semantics, which 1702 are defined in <a href="#Part2" id="rfc.xref.Part2.12"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>, and a target resource upon which to apply those semantics. A URI reference (<a href="#uri" title="Uniform Resource Identifiers">Section 2.8</a>) is typically used as an identifier for the "target resource", which a user agent would resolve to its absolute form in order 1703 to obtain the "target URI". The target URI excludes the reference's fragment identifier component, if any, since fragment 1704 identifiers are reserved for client-side processing (<a href="#RFC3986" id="rfc.xref.RFC3986.18"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.5">Section 3.5</a>). 1702 are defined in <a href="#Part2" id="rfc.xref.Part2.12"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>, and a target resource upon which to apply those semantics. A URI reference (<a href="#uri" title="Uniform Resource Identifiers">Section 2.8</a>) is typically used as an identifier for the "<dfn>target resource</dfn>", which a user agent would resolve to its absolute form in order to obtain the "<dfn>target URI</dfn>". The target URI excludes the reference's fragment identifier component, if any, since fragment identifiers are reserved 1703 for client-side processing (<a href="#RFC3986" id="rfc.xref.RFC3986.18"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.5">Section 3.5</a>). 1705 1704 </p> 1706 1705 <p id="rfc.section.5.1.p.3">HTTP intermediaries obtain the request semantics and target URI from the request-line of an incoming request message.</p> … … 1751 1750 <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 1752 1751 cache, if possible, or make the same request on the client's behalf to either the next inbound proxy server or directly to 1753 the origin server indicated by the request-target. Requirements on such "forwarding" of messages are defined in <a href="# intermediary.forwarding" title="IntermediaryForwarding">Section 5.6</a>.1752 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.6</a>. 1754 1753 </p> 1755 1754 </div> … … 1809 1808 <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a> <a id="effective.request.uri" href="#effective.request.uri">Effective Request URI</a></h2> 1810 1809 <p id="rfc.section.5.5.p.1">A server that receives an HTTP request message <em class="bcp14">MUST</em> reconstruct the user agent's original target URI, based on the pieces of information learned from the request-target, <a href="#header.host" class="smpl">Host</a> header field, and connection context, in order to identify the intended target resource and properly service the request. 1811 The URI derived from this reconstruction process is referred to as the " effective request URI".1810 The URI derived from this reconstruction process is referred to as the "<dfn>effective request URI</dfn>". 1812 1811 </p> 1813 1812 <p id="rfc.section.5.5.p.2">For a user agent, the effective request URI is the target URI.</p> … … 1844 1843 the effective request URI's authority component. 1845 1844 </p> 1846 <h2 id="rfc.section.5.6"><a href="#rfc.section.5.6">5.6</a> <a id=" intermediary.forwarding" href="#intermediary.forwarding">IntermediaryForwarding</a></h2>1845 <h2 id="rfc.section.5.6"><a href="#rfc.section.5.6">5.6</a> <a id="message.forwarding" href="#message.forwarding">Message Forwarding</a></h2> 1847 1846 <p id="rfc.section.5.6.p.1">As described in <a href="#intermediaries" title="Intermediaries">Section 2.4</a>, intermediaries can serve a variety of roles in the processing of HTTP requests and responses. Some intermediaries are used 1848 1847 to improve performance or availability. Others are used for access control or to filter content. Since an HTTP stream has … … 1852 1851 <p id="rfc.section.5.6.p.2">In order to avoid request 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, or literal IP addresses. 1853 1852 </p> 1854 <p id="rfc.section.5.6.p.3">If a proxy receives a request-target with 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 when forwarding the request. A proxy <em class="bcp14">MUST NOT</em> change the host name if it is a fully qualified domain name.1855 </p> 1856 <p id="rfc.section.5.6.p.4">A non-transforming proxy <em class="bcp14">MUST NOT</em> rewritethe "path-absolute" and "query" parts of the received request-target when forwarding it to the next inbound server,1853 <p id="rfc.section.5.6.p.3">If a proxy receives a request-target with a host name that is not a fully qualified domain name, it <em class="bcp14">MAY</em> add its own domain to the host name it received when forwarding the request. A proxy <em class="bcp14">MUST NOT</em> change the host name if it is a fully qualified domain name. 1854 </p> 1855 <p id="rfc.section.5.6.p.4">A non-transforming proxy <em class="bcp14">MUST NOT</em> modify the "path-absolute" and "query" parts of the received request-target when forwarding it to the next inbound server, 1857 1856 except as noted above to replace an empty path with "/" or "*". 1858 1857 </p>
Note: See TracChangeset
for help on using the changeset viewer.