Ignore:
Timestamp:
May 26, 2010, 10:25:13 AM (9 years ago)
Author:
julian.reschke@…
Message:

Introduce term "effective request URI" and use it throughout; may require some more fine-tuning (see #196)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.xml

    r814 r823  
    3333  <!ENTITY qvalue                   "<xref target='Part1' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3434  <!ENTITY uri                      "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     35  <!ENTITY effective-request-uri    "<xref target='Part1' x:rel='#effective.request.uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3536  <!ENTITY compression-codings      "<xref target='Part1' x:rel='#compression.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3637  <!ENTITY transfer-codings         "<xref target='Part1' x:rel='#transfer.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    13381339<t>
    13391340   The content-coding is a characteristic of the entity identified by
    1340    the request-target. Typically, the entity-body is stored with this
     1341   the Effective Request URI (&effective-request-uri;). Typically, the entity-body is stored with this
    13411342   encoding and is only decoded before rendering or analogous usage.
    13421343   However, a non-transparent proxy &MAY; modify the content-coding if the
     
    14391440</artwork></figure>
    14401441<t>
    1441    The Content-Location value is not a replacement for the original
    1442    requested URI; it is only a statement of the location of the resource
     1442   The Content-Location value is not a replacement for the Effective
     1443   Request URI (&effective-request-uri;); it is only a statement of the location of the resource
    14431444   corresponding to this particular entity at the time of the request.
    1444    Future requests &MAY; specify the Content-Location URI as the request-target
     1445   Future requests &MAY; may be addressed to the Content-Location URI
    14451446   if the desire is to identify the source of that particular
    14461447   entity.
     
    14581459<t>
    14591460   If the Content-Location is a relative URI, the relative URI is
    1460    interpreted relative to the request-target.
     1461   interpreted relative to the Effective Request URI.
    14611462</t>
    14621463<t>
     
    31503151  </list>
    31513152</t>
     3153<t>
     3154  Partly resolved issues:
     3155  <list style="symbols">
     3156    <t>
     3157      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/196"/>:
     3158      "Term for the requested resource's URI"
     3159    </t>
     3160  </list>
     3161</t>
    31523162</section>
    31533163
Note: See TracChangeset for help on using the changeset viewer.