Ignore:
Timestamp:
21/01/13 07:43:33 (7 years ago)
Author:
fielding@…
Message:

(editorial) Fix a few cases where the term payload is used beyond the scope of a message

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2132 r2147  
    8383  <!ENTITY status-416                 "<xref target='Part5' x:rel='#status.416' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    8484  <!ENTITY p4-status-codes            "<xref target='Part4' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    85   <!ENTITY p5-status-codes            "<xref target='Part5' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     85  <!ENTITY p5-status-codes            "<xref target='Part5' x:rel='#range.response' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    8686  <!ENTITY p7-status-codes            "<xref target='Part7' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    8787  <!ENTITY p6-heuristic               "<xref target='Part6' x:rel='#heuristic.freshness' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    598598   for some bizarre reason, it is applied a second time to form the
    599599   representation.  Likewise, an origin server might choose to publish the
    600    same payload data as multiple representations that differ only in whether
     600   same data as multiple representations that differ only in whether
    601601   the coding is defined as part of <x:ref>Content-Type</x:ref> or
    602602   Content-Encoding, since some user agents will behave differently in their
     
    701701</t>
    702702<t>
    703    The following rules are used to determine such a URI for the payload of a
    704    request message:
     703   For a request message:
    705704   <list style="symbols">
    706705      <t>If the request has a <x:ref>Content-Location</x:ref> header field,
     
    714713</t>
    715714<t>
    716    The following rules, to be applied in order until a match is found, are
    717    used to determine such a URI for the payload of a response message:
     715   For a response message, the following rules are applied in order until a
     716   match is found:
    718717   <list style="numbers">
    719718      <t>If the request is GET or HEAD and the response status code is
     
    722721         <x:ref>206 (Partial Content)</x:ref>, or
    723722         <x:ref>304 (Not Modified)</x:ref>,
    724          the payload's identifier is the effective request URI
    725          (&effective-request-uri;).</t>
     723         the payload is a representation of the resource identified by the
     724         effective request URI (&effective-request-uri;).</t>
    726725      <t>If the request is GET or HEAD and the response status code is
    727726         <x:ref>203 (Non-Authoritative Information)</x:ref>, the payload is
    728          intended to be a representation of the <x:ref>target resource</x:ref>
    729          that has been modified by an intermediary.</t>
     727         a potentially modified or enhanced representation of the
     728         <x:ref>target resource</x:ref> as provided by an intermediary.</t>
    730729      <t>If the response has a <x:ref>Content-Location</x:ref> header field
    731730         and its field-value is a reference to the same URI as the effective
    732          request URI, the payload's identifier is the effective request URI.</t>
     731         request URI, the payload is a representation of the resource
     732         identified by the effective request URI.</t>
    733733      <t>If the response has a <x:ref>Content-Location</x:ref> header field
    734734         and its field-value is a reference to a URI different from the
     
    747747<t>
    748748   The "Content-Location" header field references a URI that can be used
    749    as a specific identifier for the representation in this message payload.
    750    In other words, if one were to perform a GET on this URI at the time
     749   as an identifier for a specific resource corresponding to the
     750   representation in this message's payload.
     751   In other words, if one were to perform a GET request on this URI at the time
    751752   of this message's generation, then a <x:ref>200 (OK)</x:ref> response would
    752753   contain the same representation that is enclosed as payload in this message.
     
    780781   If Content-Location is included in a <x:ref>2xx (Successful)</x:ref>
    781782   response message and its field-value refers to a URI that differs from the
    782    effective request URI, then the origin server claims that the field-value
    783    is an identifier for the representation enclosed as the payload. Such a
    784    claim can only be trusted if both identifiers share the same resource
    785    owner, which cannot be programmatically determined via HTTP.
     783   effective request URI, then the origin server claims that the URI
     784   is an identifier for a different resource corresponding to the enclosed
     785   representation. Such a claim can only be trusted if both identifiers share
     786   the same resource owner, which cannot be programmatically determined via
     787   HTTP.
    786788   <list style="symbols">
    787789    <t>For a response to a GET or HEAD request, this is an indication that the
     
    45204522<t>
    45214523   Because commas (",") are used as a generic delimiter between field-values,
    4522    they need to be treated with care if they are allowed in the field-value's
    4523    payload. Typically, components that might contain a comma are protected with
    4524    double-quotes using the quoted-string ABNF production (&field-components;). 
     4524   they need to be treated with care if they are allowed in the field-value.
     4525   Typically, components that might contain a comma are protected with
     4526   double-quotes using the quoted-string ABNF production (&field-components;).
    45254527</t>
    45264528<t>
Note: See TracChangeset for help on using the changeset viewer.