Changeset 1794 for draft-ietf-httpbis/latest/p6-cache.html
- Timestamp:
- 16/07/12 02:02:32 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r1793 r1794 452 452 } 453 453 @bottom-center { 454 content: "Expires January 1 6, 2013";454 content: "Expires January 17, 2013"; 455 455 } 456 456 @bottom-right { … … 491 491 <link href="p5-range.html" rel="prev"> 492 492 <link href="p7-auth.html" rel="next"> 493 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.584, 2012-06-24 15:59:38, XSLT vendor: SAXON 8.9from Saxonica http://www.saxonica.com/">493 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.584, 2012-06-24 15:59:38, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/"> 494 494 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 495 495 <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="2012-07-1 5">500 <meta name="dct.issued" scheme="ISO8601" content="2012-07-16"> 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. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 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: January 1 6, 2013</td>526 <td class="left">Expires: January 17, 2013</td> 527 527 <td class="right">M. Nottingham, Editor</td> 528 528 </tr> … … 541 541 <tr> 542 542 <td class="left"></td> 543 <td class="right">July 1 5, 2012</td>543 <td class="right">July 16, 2012</td> 544 544 </tr> 545 545 </tbody> … … 570 570 in progress”. 571 571 </p> 572 <p>This Internet-Draft will expire on January 1 6, 2013.</p>572 <p>This Internet-Draft will expire on January 17, 2013.</p> 573 573 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 574 574 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1542 1542 <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a> <a id="header.vary" href="#header.vary">Vary</a></h2> 1543 1543 <p id="rfc.section.7.5.p.1">The "Vary" header field conveys the set of header fields that were used to select the representation.</p> 1544 <p id="rfc.section.7.5.p.2">Caches use this information, in part, to determine whether a stored response can be used to satisfy a given request; see <a href="#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a>. determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request 1545 without validation; see <a href="#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a>. 1544 <p id="rfc.section.7.5.p.2">Caches use this information, in part, to determine whether a stored response can be used to satisfy a given request; see <a href="#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a>. 1546 1545 </p> 1547 1546 <p id="rfc.section.7.5.p.3">In uncacheable or stale responses, the Vary field value advises the user agent about the criteria that were used to select
Note: See TracChangeset
for help on using the changeset viewer.