Changeset 2041 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

08/12/12 08:00:42 (10 years ago)

Author:

fielding@…

Message:

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

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (3 diffs)

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -34 +34 @@
   <!ENTITY effective-request-uri      "<xref target='Part1' x:rel='#effective.request.uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY intermediaries             "<xref target='Part1' x:rel='#intermediaries' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
+  <!ENTITY transformations            "<xref target='Part1' x:rel='#message.transformations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY chunked-encoding           "<xref target='Part1' x:rel='#chunked.encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY http-url                   "<xref target='Part1' x:rel='#http-url' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -582 +583 @@
 </t>
 <t>
-   A transforming proxy &MAY; modify the content coding if the
-   new coding is known to be acceptable to the recipient, unless the
-   "no-transform" cache-control directive is present in the message.
-</t>
-<t>
    If the media type includes an inherent encoding, such as a data format
    that is always compressed, then that encoding would not be restated as 
@@ -2784 +2780 @@
   <x:anchor-alias value="203 (Non-Authoritative Information)"/>
 <t>
-   The representation in the response has been transformed or otherwise
-   modified by a transforming proxy (&intermediaries;).  Note that the
-   behavior of transforming intermediaries is controlled by the no-transform
-   Cache-Control directive (&header-cache-control;).
-</t>
-<t>
-   This status code is only appropriate when the response status code would
-   have been <x:ref>200 (OK)</x:ref> otherwise. When the status code before
-   transformation would have been different, the 214 Transformation Applied
-   warn-code (&header-warning;) is appropriate.
-</t>
-<t>
-   Caches &MAY; use a heuristic (see &p6-heuristic;) to determine 
-   freshness for 203 responses.
+   The request was successful but the enclosed payload has been modified
+   from that of the origin server's <x:ref>200 (OK)</x:ref> response by a
+   transforming proxy (&transformations;). This status code allows the proxy
+   to notify recipients when a transformation has been applied, since that
+   knowledge might impact later decisions regarding the content.
+   For example, future cache validation requests for the content might only
+   be applicable along the same request path (through the same proxies).
+</t>
+<t>
+   The 203 response is similar to the Warning code of 214 Transformation
+   Applied (&header-warning;), which has the advantage of being applicable
+   to responses with any status code.
 </t>
 </section>