Ignore:
Timestamp:
Mar 12, 2012, 1:37:08 AM (8 years ago)
Author:
fielding@…
Message:

user agents always parse relative to the original URI, not the effective URI

File:
1 edited

Legend:

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

    r1588 r1589  
    10531053</pre><p id="rfc.section.2.7.p.4">Each protocol element in HTTP that allows a URI reference will indicate in its ABNF production whether the element allows
    10541054         any form of reference (URI-reference), only a URI in absolute form (absolute-URI), only the path and optional query components,
    1055          or some combination of the above. Unless otherwise indicated, URI references are parsed relative to the effective request
    1056          URI, which defines the default base URI for references in both the request and its corresponding response.
     1055         or some combination of the above. Unless otherwise indicated, URI references are parsed relative to the request's target URI
     1056         (<a href="#target-resource" title="Identifying a Target Resource">Section&nbsp;5.1</a>), if known by the recipient, or the effective request URI (<a href="#effective.request.uri" title="Effective Request URI">Section&nbsp;5.5</a>).
    10571057      </p>
    10581058      <h3 id="rfc.section.2.7.1"><a href="#rfc.section.2.7.1">2.7.1</a>&nbsp;<a id="http.uri" href="#http.uri">http URI scheme</a></h3>
Note: See TracChangeset for help on using the changeset viewer.