Changeset 2264


Ignore:
Timestamp:
May 19, 2013, 6:43:03 PM (6 years ago)
Author:
mnot@…
Message:

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

Location:
draft-ietf-httpbis/latest
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p4-conditional.html

    r2255 r2264  
    449449  }
    450450  @bottom-center {
    451        content: "Expires November 20, 2013";
     451       content: "Expires November 21, 2013";
    452452  }
    453453  @bottom-right {
     
    486486      <link href="p2-semantics.html" rel="prev">
    487487      <link href="p5-range.html" rel="next">
    488       <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/">
     488      <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/">
    489489      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    490490      <meta name="dct.creator" content="Fielding, R.">
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2013-05-19">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-05-20">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    495495      <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.">
     
    517517            </tr>
    518518            <tr>
    519                <td class="left">Expires: November 20, 2013</td>
    520                <td class="right">May 19, 2013</td>
     519               <td class="left">Expires: November 21, 2013</td>
     520               <td class="right">May 20, 2013</td>
    521521            </tr>
    522522         </tbody>
     
    545545         in progress”.
    546546      </p>
    547       <p>This Internet-Draft will expire on November 20, 2013.</p>
     547      <p>This Internet-Draft will expire on November 21, 2013.</p>
    548548      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    549549      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
  • draft-ietf-httpbis/latest/p6-cache.html

    r2251 r2264  
    452452  }
    453453  @bottom-center {
    454        content: "Expires November 19, 2013";
     454       content: "Expires November 21, 2013";
    455455  }
    456456  @bottom-right {
     
    492492      <link href="p5-range.html" rel="prev">
    493493      <link href="p7-auth.html" rel="next">
    494       <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/">
     494      <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/">
    495495      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    496496      <meta name="dct.creator" content="Fielding, R.">
     
    498498      <meta name="dct.creator" content="Reschke, J. F.">
    499499      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    500       <meta name="dct.issued" scheme="ISO8601" content="2013-05-18">
     500      <meta name="dct.issued" scheme="ISO8601" content="2013-05-20">
    501501      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    502502      <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.">
     
    524524            </tr>
    525525            <tr>
    526                <td class="left">Expires: November 19, 2013</td>
     526               <td class="left">Expires: November 21, 2013</td>
    527527               <td class="right">J. Reschke, Editor</td>
    528528            </tr>
     
    533533            <tr>
    534534               <td class="left"></td>
    535                <td class="right">May 18, 2013</td>
     535               <td class="right">May 20, 2013</td>
    536536            </tr>
    537537         </tbody>
     
    559559         in progress”.
    560560      </p>
    561       <p>This Internet-Draft will expire on November 19, 2013.</p>
     561      <p>This Internet-Draft will expire on November 21, 2013.</p>
    562562      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    563563      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    10861086      </p>
    10871087      <p id="rfc.section.4.3.p.5">The stored response with matching selecting header fields is known as the selected response.</p>
    1088       <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
    1089          (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>.
     1088      <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
     1089         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>.
    10901090      </p>
    10911091      <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

    r2250 r2264  
    924924<t>
    925925   If multiple selected responses are available (potentially including
    926    responses without a Vary header), the most recent response (as determined by
    927    the <x:ref>Date</x:ref> header field) is used; see <xref
    928    target="constructing.responses.from.caches"/>.
     926   responses without a Vary header), the cache will need to choose one to use.
     927   When a selecting header has a known mechanism for doing so (e.g., qvalues on
     928   <x:ref>Accept</x:ref> and similar request headers), that mechanism &MAY; be
     929   used to select preferred responses; of the remainder, the most recent
     930   response (as determined by the <x:ref>Date</x:ref> header field) is used, as
     931   per <xref target="constructing.responses.from.caches"/>.
    929932</t>
    930933<t>
Note: See TracChangeset for help on using the changeset viewer.