Ignore:
Timestamp:
08/12/12 08:00:42 (8 years ago)
Author:
fielding@…
Message:

remove irrelevant details from transforming proxy requirements now obsolete due to introduction of payload terminology; addresses #418

File:
1 edited

Legend:

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

    r2031 r2041  
    3434  <!ENTITY effective-request-uri      "<xref target='Part1' x:rel='#effective.request.uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3535  <!ENTITY intermediaries             "<xref target='Part1' x:rel='#intermediaries' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     36  <!ENTITY transformations            "<xref target='Part1' x:rel='#message.transformations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3637  <!ENTITY chunked-encoding           "<xref target='Part1' x:rel='#chunked.encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3738  <!ENTITY http-url                   "<xref target='Part1' x:rel='#http-url' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    582583</t>
    583584<t>
    584    A transforming proxy &MAY; modify the content coding if the
    585    new coding is known to be acceptable to the recipient, unless the
    586    "no-transform" cache-control directive is present in the message.
    587 </t>
    588 <t>
    589585   If the media type includes an inherent encoding, such as a data format
    590586   that is always compressed, then that encoding would not be restated as
     
    27842780  <x:anchor-alias value="203 (Non-Authoritative Information)"/>
    27852781<t>
    2786    The representation in the response has been transformed or otherwise
    2787    modified by a transforming proxy (&intermediaries;).  Note that the
    2788    behavior of transforming intermediaries is controlled by the no-transform
    2789    Cache-Control directive (&header-cache-control;).
    2790 </t>
    2791 <t>
    2792    This status code is only appropriate when the response status code would
    2793    have been <x:ref>200 (OK)</x:ref> otherwise. When the status code before
    2794    transformation would have been different, the 214 Transformation Applied
    2795    warn-code (&header-warning;) is appropriate.
    2796 </t>
    2797 <t>
    2798    Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
    2799    freshness for 203 responses.
     2782   The request was successful but the enclosed payload has been modified
     2783   from that of the origin server's <x:ref>200 (OK)</x:ref> response by a
     2784   transforming proxy (&transformations;). This status code allows the proxy
     2785   to notify recipients when a transformation has been applied, since that
     2786   knowledge might impact later decisions regarding the content.
     2787   For example, future cache validation requests for the content might only
     2788   be applicable along the same request path (through the same proxies).
     2789</t>
     2790<t>
     2791   The 203 response is similar to the Warning code of 214 Transformation
     2792   Applied (&header-warning;), which has the advantage of being applicable
     2793   to responses with any status code.
    28002794</t>
    28012795</section>
Note: See TracChangeset for help on using the changeset viewer.