Changeset 2264 for draft-ietf-httpbis/latest
- Timestamp:
- 20/05/13 01:43:03 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.html
r2255 r2264 449 449 } 450 450 @bottom-center { 451 content: "Expires November 2 0, 2013";451 content: "Expires November 21, 2013"; 452 452 } 453 453 @bottom-right { … … 486 486 <link href="p2-semantics.html" rel="prev"> 487 487 <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.9from 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/"> 489 489 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 490 490 <meta name="dct.creator" content="Fielding, R."> 491 491 <meta name="dct.creator" content="Reschke, J. F."> 492 492 <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"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 495 495 <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> 518 518 <tr> 519 <td class="left">Expires: November 2 0, 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> 521 521 </tr> 522 522 </tbody> … … 545 545 in progress”. 546 546 </p> 547 <p>This Internet-Draft will expire on November 2 0, 2013.</p>547 <p>This Internet-Draft will expire on November 21, 2013.</p> 548 548 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 549 549 <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 452 452 } 453 453 @bottom-center { 454 content: "Expires November 19, 2013";454 content: "Expires November 21, 2013"; 455 455 } 456 456 @bottom-right { … … 492 492 <link href="p5-range.html" rel="prev"> 493 493 <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.9from 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/"> 495 495 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 496 496 <meta name="dct.creator" content="Fielding, R."> … … 498 498 <meta name="dct.creator" content="Reschke, J. F."> 499 499 <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"> 501 501 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 502 502 <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> 525 525 <tr> 526 <td class="left">Expires: November 19, 2013</td>526 <td class="left">Expires: November 21, 2013</td> 527 527 <td class="right">J. Reschke, Editor</td> 528 528 </tr> … … 533 533 <tr> 534 534 <td class="left"></td> 535 <td class="right">May 18, 2013</td>535 <td class="right">May 20, 2013</td> 536 536 </tr> 537 537 </tbody> … … 559 559 in progress”. 560 560 </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> 562 562 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 563 563 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1086 1086 </p> 1087 1087 <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 response1089 (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 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 4</a>. 1090 1090 </p> 1091 1091 <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 924 924 <t> 925 925 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"/>. 929 932 </t> 930 933 <t>
Note: See TracChangeset
for help on using the changeset viewer.