Changeset 1833


Ignore:
Timestamp:
Aug 19, 2012, 5:10:23 PM (7 years ago)
Author:
fielding@…
Message:

mark-up some definitions and clarify a heading

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

Legend:

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

    r1832 r1833  
    639639               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.host">Host</a></li>
    640640               <li><a href="#rfc.section.5.5">5.5</a>&nbsp;&nbsp;&nbsp;<a href="#effective.request.uri">Effective Request URI</a></li>
    641                <li><a href="#rfc.section.5.6">5.6</a>&nbsp;&nbsp;&nbsp;<a href="#intermediary.forwarding">Intermediary Forwarding</a><ul>
     641               <li><a href="#rfc.section.5.6">5.6</a>&nbsp;&nbsp;&nbsp;<a href="#message.forwarding">Message Forwarding</a><ul>
    642642                     <li><a href="#rfc.section.5.6.1">5.6.1</a>&nbsp;&nbsp;&nbsp;<a href="#end-to-end.and.hop-by-hop.header-fields">End-to-end and Hop-by-hop Header Fields</a></li>
    643643                     <li><a href="#rfc.section.5.6.2">5.6.2</a>&nbsp;&nbsp;&nbsp;<a href="#non-modifiable.header-fields">Non-modifiable Header Fields</a></li>
     
    17001700      </p>
    17011701      <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&nbsp;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&nbsp;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>).
    17051704      </p>
    17061705      <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>
     
    17511750         <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
    17521751            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="Intermediary Forwarding">Section&nbsp;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&nbsp;5.6</a>.
    17541753         </p>
    17551754      </div>
     
    18091808      <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a id="effective.request.uri" href="#effective.request.uri">Effective Request URI</a></h2>
    18101809      <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>".
    18121811      </p>
    18131812      <p id="rfc.section.5.5.p.2">For a user agent, the effective request URI is the target URI.</p>
     
    18441843         the effective request URI's authority component.
    18451844      </p>
    1846       <h2 id="rfc.section.5.6"><a href="#rfc.section.5.6">5.6</a>&nbsp;<a id="intermediary.forwarding" href="#intermediary.forwarding">Intermediary Forwarding</a></h2>
     1845      <h2 id="rfc.section.5.6"><a href="#rfc.section.5.6">5.6</a>&nbsp;<a id="message.forwarding" href="#message.forwarding">Message Forwarding</a></h2>
    18471846      <p id="rfc.section.5.6.p.1">As described in <a href="#intermediaries" title="Intermediaries">Section&nbsp;2.4</a>, intermediaries can serve a variety of roles in the processing of HTTP requests and responses. Some intermediaries are used
    18481847         to improve performance or availability. Others are used for access control or to filter content. Since an HTTP stream has
     
    18521851      <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.
    18531852      </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> rewrite the "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,
    18571856         except as noted above to replace an empty path with "/" or "*".
    18581857      </p>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1832 r1833  
    21452145   <xref target="Part2"/>, and a target resource upon which to apply those
    21462146   semantics.  A URI reference (<xref target="uri"/>) is typically used as
    2147    an identifier for the "target resource", which a user agent would resolve
    2148    to its absolute form in order to obtain the "target URI".  The target URI
     2147   an identifier for the "<x:dfn>target resource</x:dfn>", which a user agent
     2148   would resolve to its absolute form in order to obtain the
     2149   "<x:dfn>target URI</x:dfn>".  The target URI
    21492150   excludes the reference's fragment identifier component, if any,
    21502151   since fragment identifiers are reserved for client-side processing
     
    22462247   the next inbound proxy server or directly to the origin server indicated
    22472248   by the request-target.  Requirements on such "forwarding" of messages are
    2248    defined in <xref target="intermediary.forwarding"/>.
     2249   defined in <xref target="message.forwarding"/>.
    22492250</t>
    22502251<t>
     
    23742375   connection context, in order to identify the intended target resource and
    23752376   properly service the request. The URI derived from this reconstruction
    2376    process is referred to as the "effective request URI".
     2377   process is referred to as the "<x:dfn>effective request URI</x:dfn>".
    23772378</t>
    23782379<t>
     
    24572458</section>
    24582459
    2459 <section title="Intermediary Forwarding" anchor="intermediary.forwarding">
     2460<section title="Message Forwarding" anchor="message.forwarding">
    24602461<t>
    24612462   As described in <xref target="intermediaries"/>, intermediaries can serve
     
    24742475<t>
    24752476   If a proxy receives a request-target with a host name that is not a
    2476    fully qualified domain name, it &MAY; add its domain to the host name
     2477   fully qualified domain name, it &MAY; add its own domain to the host name
    24772478   it received when forwarding the request.  A proxy &MUST-NOT; change the
    24782479   host name if it is a fully qualified domain name.
    24792480</t>
    24802481<t>
    2481    A non-transforming proxy &MUST-NOT; rewrite the "path-absolute" and "query"
     2482   A non-transforming proxy &MUST-NOT; modify the "path-absolute" and "query"
    24822483   parts of the received request-target when forwarding it to the next inbound
    24832484   server, except as noted above to replace an empty path with "/" or "*".
Note: See TracChangeset for help on using the changeset viewer.