Changeset 2264 for draft-ietf-httpbis/latest

Timestamp:

20/05/13 01:43:03 (7 years ago)

Author:

mnot@…

Message:

Allow selecting headers to be smart about selecting a negotiated representation; see #453

Location:

draft-ietf-httpbis/latest

Files:

• p4-conditional.html (modified) (4 diffs)
• p6-cache.html (modified) (7 diffs)
• p6-cache.xml (modified) (1 diff)

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

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires November 20, 2013"; 
+       content: "Expires November 21, 2013"; 
   } 
   @bottom-right {
@@ -486 +486 @@
       <link href="p2-semantics.html" rel="prev">
       <link href="p5-range.html" rel="next">
-      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.594, 2013/04/30 16:11:28, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
+      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.594, 2013/04/30 16:11:28, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/">
       <link rel="schema.dct" href="http://purl.org/dc/terms/">
       <meta name="dct.creator" content="Fielding, R.">
       <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="2013-05-19">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-05-20">
       <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, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false.">
@@ -517 +517 @@
             </tr>
             <tr>
-               <td class="left">Expires: November 20, 2013</td>
-               <td class="right">May 19, 2013</td>
+               <td class="left">Expires: November 21, 2013</td>
+               <td class="right">May 20, 2013</td>
             </tr>
          </tbody>
@@ -545 +545 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on November 20, 2013.</p>
+      <p>This Internet-Draft will expire on November 21, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>

draft-ietf-httpbis/latest/p6-cache.html

@@ -452 +452 @@
   } 
   @bottom-center {
-       content: "Expires November 19, 2013"; 
+       content: "Expires November 21, 2013"; 
   } 
   @bottom-right {
@@ -492 +492 @@
       <link href="p5-range.html" rel="prev">
       <link href="p7-auth.html" rel="next">
-      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.594, 2013/04/30 16:11:28, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
+      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.594, 2013/04/30 16:11:28, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/">
       <link rel="schema.dct" href="http://purl.org/dc/terms/">
       <meta name="dct.creator" content="Fielding, R.">
@@ -498 +498 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-05-18">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-05-20">
       <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, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
@@ -524 +524 @@
             </tr>
             <tr>
-               <td class="left">Expires: November 19, 2013</td>
+               <td class="left">Expires: November 21, 2013</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -533 +533 @@
             <tr>
                <td class="left"></td>
-               <td class="right">May 18, 2013</td>
+               <td class="right">May 20, 2013</td>
             </tr>
          </tbody>
@@ -559 +559 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on November 19, 2013.</p>
+      <p>This Internet-Draft will expire on November 21, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1086 +1086 @@
       </p>
       <p id="rfc.section.4.3.p.5">The stored response with matching selecting header fields is known as the selected response.</p>
-      <p id="rfc.section.4.3.p.6">If multiple selected responses are available (potentially including responses without a Vary header), the most recent response
-         (as determined by the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field) is used; see <a href="#constructing.responses.from.caches" title="Constructing Responses from Caches">Section&nbsp;4</a>.
+      <p id="rfc.section.4.3.p.6">If multiple selected responses are available (potentially including responses without a Vary header), the cache will need
+         to choose one to use. When a selecting header has a known mechanism for doing so (e.g., qvalues on Accept and similar request headers), that mechanism <em class="bcp14">MAY</em> be used to select preferred responses; of the remainder, the most recent response (as determined by the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field) is used, as per <a href="#constructing.responses.from.caches" title="Constructing Responses from Caches">Section&nbsp;4</a>.
       </p>
       <p id="rfc.section.4.3.p.7">If no selected response is available, the cache cannot satisfy the presented request. Typically, it is forwarded to the origin

draft-ietf-httpbis/latest/p6-cache.xml

@@ -924 +924 @@
 <t>
    If multiple selected responses are available (potentially including
-   responses without a Vary header), the most recent response (as determined by
-   the <x:ref>Date</x:ref> header field) is used; see <xref
-   target="constructing.responses.from.caches"/>.
+   responses without a Vary header), the cache will need to choose one to use.
+   When a selecting header has a known mechanism for doing so (e.g., qvalues on
+   <x:ref>Accept</x:ref> and similar request headers), that mechanism &MAY; be
+   used to select preferred responses; of the remainder, the most recent
+   response (as determined by the <x:ref>Date</x:ref> header field) is used, as
+   per <xref target="constructing.responses.from.caches"/>.
 </t>
 <t>