Changeset 960

Timestamp:

28/07/10 08:36:00 (12 years ago)

Author:

fielding@…

Message:

Reduce new MUST requirement to forward a 304 on an outbound
conditional request to MAY, since there is no need for a
new requirement here (the explanation is enough to motivate).
Related to [860].

Location:

draft-ietf-httpbis/latest

Files:

• p4-conditional.html (modified) (5 diffs)
• p4-conditional.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p4-conditional.html

@@ -400 +400 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2010-07-27">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-07-28">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests.">
@@ -426 +426 @@
             </tr>
             <tr>
-               <td class="left">Expires: January 28, 2011</td>
+               <td class="left">Expires: January 29, 2011</td>
                <td class="right">J. Mogul</td>
             </tr>
@@ -483 +483 @@
             <tr>
                <td class="left"></td>
-               <td class="right">July 27, 2010</td>
+               <td class="right">July 28, 2010</td>
             </tr>
          </tbody>
@@ -509 +509 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire in January 28, 2011.</p>
+      <p>This Internet-Draft will expire in January 29, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -693 +693 @@
       </p>
       <p id="rfc.section.3.1.p.4">If a 304 response includes an entity-tag that indicates a representation not currently cached, then the recipient <em class="bcp14">MUST NOT</em> use the 304 to update its own cache. If that conditional request originated with an outbound client, such as a user agent
-         with its own cache sending a conditional GET to a shared proxy, then the 304 response <em class="bcp14">MUST</em> be forwarded to the outbound client. Otherwise, disregard the response and repeat the request without the conditional.
+         with its own cache sending a conditional GET to a shared proxy, then the 304 response <em class="bcp14">MAY</em> be forwarded to the outbound client. Otherwise, disregard the response and repeat the request without the conditional.
       </p>
       <p id="rfc.section.3.1.p.5">If a cache uses a received 304 response to update a cache entry, the cache <em class="bcp14">MUST</em> update the entry to reflect any new field values given in the response.

draft-ietf-httpbis/latest/p4-conditional.xml

@@ -429 +429 @@
    use the 304 to update its own cache.  If that conditional request originated
    with an outbound client, such as a user agent with its own cache sending a
-   conditional GET to a shared proxy, then the 304 response &MUST; be
+   conditional GET to a shared proxy, then the 304 response &MAY; be
    forwarded to the outbound client.  Otherwise, disregard the response
    and repeat the request without the conditional.