Ignore:
Timestamp:
Nov 14, 2008, 4:44:55 PM (11 years ago)
Author:
julian.reschke@…
Message:

Merge in Roy's changes wrt Introduction and HTTP Architecture, replace Request-URI by request-target and relative-URI by partial-URI throughout.

File:
1 edited

Legend:

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

    r385 r391  
    281281  <x:anchor-alias value="Last-Modified"/>
    282282  <x:anchor-alias value="message-header"/>
    283   <x:anchor-alias value="relativeURI"/>
     283  <x:anchor-alias value="partial-URI"/>
    284284  The ABNF rules below are defined in other parts:
    285285</t>
     
    287287  <x:ref>absolute-URI</x:ref>   = &lt;absolute-URI, defined in &uri;&gt;
    288288  <x:ref>Content-Length</x:ref> = &lt;Content-Length, defined in &header-content-length;&gt;
    289   <x:ref>relativeURI</x:ref>    = &lt;relativeURI, defined in &uri;&gt;
    290289  <x:ref>message-header</x:ref> = &lt;message-header, defined in &message-headers;&gt;
     290  <x:ref>partial-URI</x:ref>    = &lt;partial-URI, defined in &uri;&gt;
    291291</artwork></figure>
    292292<figure><!--Part4--><artwork type="abnf2616">
     
    12841284<t>
    12851285   The content-coding is a characteristic of the entity identified by
    1286    the Request-URI. Typically, the entity-body is stored with this
     1286   the request-target. Typically, the entity-body is stored with this
    12871287   encoding and is only decoded before rendering or analogous usage.
    12881288   However, a non-transparent proxy &MAY; modify the content-coding if the
     
    13821382                    <x:ref>Content-Location-v</x:ref>
    13831383  <x:ref>Content-Location-v</x:ref> =
    1384                     <x:ref>absolute-URI</x:ref> / <x:ref>relativeURI</x:ref>
     1384                    <x:ref>absolute-URI</x:ref> / <x:ref>partial-URI</x:ref>
    13851385</artwork></figure>
    13861386<t>
     
    13921392   requested URI; it is only a statement of the location of the resource
    13931393   corresponding to this particular entity at the time of the request.
    1394    Future requests &MAY; specify the Content-Location URI as the request-URI
     1394   Future requests &MAY; specify the Content-Location URI as the request-target
    13951395   if the desire is to identify the source of that particular
    13961396   entity.
     
    14051405<t>
    14061406   If the Content-Location is a relative URI, the relative URI is
    1407    interpreted relative to the Request-URI.
     1407   interpreted relative to the request-target.
    14081408</t>
    14091409<t>
Note: See TracChangeset for help on using the changeset viewer.