Changeset 756 for draft-ietf-httpbis/latest/p4-conditional.html
- Timestamp:
- 02/02/10 12:04:50 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.html
r755 r756 400 400 <meta name="dct.creator" content="Reschke, J. F."> 401 401 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 402 <meta name="dct.issued" scheme="ISO8601" content="2010-02-0 1">402 <meta name="dct.issued" scheme="ISO8601" content="2010-02-02"> 403 403 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 404 404 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> … … 426 426 </tr> 427 427 <tr> 428 <td class="left">Expires: August 5, 2010</td>428 <td class="left">Expires: August 6, 2010</td> 429 429 <td class="right">J. Mogul</td> 430 430 </tr> … … 483 483 <tr> 484 484 <td class="left"></td> 485 <td class="right">February 1, 2010</td>485 <td class="right">February 2, 2010</td> 486 486 </tr> 487 487 </tbody> … … 513 513 <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>. 514 514 </p> 515 <p>This Internet-Draft will expire in August 5, 2010.</p>515 <p>This Internet-Draft will expire in August 6, 2010.</p> 516 516 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 517 517 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 819 819 </p> 820 820 <div class="note" id="rfc.section.5.p.5"> 821 <p> <b>Note:</b> in order to provide semantically transparent caching, an origin server must avoid reusing a specific strong entity tag value821 <p> <b>Note:</b> In order to provide semantically transparent caching, an origin server must avoid reusing a specific strong entity tag value 822 822 for two different entities, or reusing a specific weak entity tag value for two semantically different entities. Cache entries 823 823 might persist for arbitrarily long periods, regardless of expiration times, so it might be inappropriate to expect that a
Note: See TracChangeset
for help on using the changeset viewer.