Changeset 763 for draft-ietf-httpbis/latest/p6-cache.html
- Timestamp:
- 28/02/10 15:22:53 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r756 r763 402 402 <meta name="dct.creator" content="Reschke, J. F."> 403 403 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 404 <meta name="dct.issued" scheme="ISO8601" content="2010-02- 02">404 <meta name="dct.issued" scheme="ISO8601" content="2010-02-28"> 405 405 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 406 406 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. 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."> … … 428 428 </tr> 429 429 <tr> 430 <td class="left">Expires: August 6, 2010</td>430 <td class="left">Expires: September 1, 2010</td> 431 431 <td class="right">J. Mogul</td> 432 432 </tr> … … 489 489 <tr> 490 490 <td class="left"></td> 491 <td class="right">February 2 , 2010</td>491 <td class="right">February 28, 2010</td> 492 492 </tr> 493 493 </tbody> … … 519 519 <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>. 520 520 </p> 521 <p>This Internet-Draft will expire in August 6, 2010.</p>521 <p>This Internet-Draft will expire in September 1, 2010.</p> 522 522 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 523 523 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1389 1389 it important that users not be presented with error messages or warning messages when they use navigation controls (such as 1390 1390 BACK) to view previously fetched resources. Even though sometimes such resources ought not be cached, or ought to expire quickly, 1391 user interface considerations may force service authors to resort to other means of preventing caching (e.g. "once-only" URLs)1392 in order not to suffer the effects of improperly functioning history mechanisms.1391 user interface considerations may force service authors to resort to other means of preventing caching (e.g., "once-only" 1392 URLs) in order not to suffer the effects of improperly functioning history mechanisms. 1393 1393 </p> 1394 1394 </div>
Note: See TracChangeset
for help on using the changeset viewer.