Ticket #296: 296.diff

p1-messaging.xml

@@ -33 +33 @@
   <!ENTITY status-codes           "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY status-100             "<xref target='Part2' x:rel='#status.100' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY status-1xx             "<xref target='Part2' x:rel='#status.1xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
+  <!ENTITY status-203             "<xref target='Part2' x:rel='#status.203' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY status-3xx             "<xref target='Part2' x:rel='#status.3xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY status-414             "<xref target='Part2' x:rel='#status.414' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
 ]>
@@ -709 +710 @@
    organization) that selected the proxy and are beyond the scope of
    this specification.  However, when a proxy is not intended to transform
    a given message, we use the term "<x:dfn>non-transforming proxy</x:dfn>" to target
-   requirements that preserve HTTP message semantics.
+   requirements that preserve HTTP message semantics. See &status-203; and
+   &header-warning; for status and warning codes related to transformations.
 </t>
 <t><iref primary="true" item="gateway"/><iref primary="true" item="reverse proxy"/>
 <iref primary="true" item="accelerator"/>

p2-semantics.xml

@@ -28 +28 @@
   <!ENTITY basic-rules                "<xref target='Part1' x:rel='#basic.rules' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY uri                        "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!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 full-date                  "<xref target='Part1' x:rel='#date.time.formats.full.date' 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'/>">
   <!ENTITY http-version               "<xref target='Part1' x:rel='#http.version' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -1402 +1403 @@
   <iref primary="true" item="203 Non-Authoritative Information (status code)" x:for-anchor=""/>
   <iref primary="true" item="Status Codes" subitem="203 Non-Authoritative Information" x:for-anchor=""/>
 <t>
-   The returned metadata in the header fields is not the
-   definitive set as available from the origin server, but is gathered
-   from a local or a third-party copy. The set presented &MAY; be a subset
-   or superset of the original version. For example, including local
-   annotation information about the resource might result in a superset
-   of the metadata known by the origin server. Use of this
-   response code is not required and is only appropriate when the
-   response would otherwise be 200 (OK).
+   The representation in the response has been transformed or otherwise
+   modified by a transforming proxy (&intermediaries;).  Note that the
+   behaviour 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 200 (OK) 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.
 </t>
-
 </section>
 
 <section title="204 No Content" anchor="status.204">
@@ -3510 +3512 @@
   (<xref target="CONNECT"/>)
 </t>
 <t>
+  Broadened the definition of 203 (Non-Authoritative Information) to include
+  cases of payload transformations as well.
+  (<xref target="status.203"/>)
+</t>
+<t>
   Failed to consider that there are
   many other request methods that are safe to automatically redirect,
   and further that the user agent is able to make that determination
@@ -4128 +4135 @@
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/294"/>:
       "clarify 403 forbidden"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/296"/>:
+      "Clarify 203 Non-Authoritative Information"
+    </t>
   </list>
 </t>
 </section>