Changeset 969 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 31/07/10 01:06:01 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r965 r969 280 280 <list> 281 281 <t>The time at which the origin server intends that a representation 282 shouldno longer be returned by a cache without further validation.</t>282 no longer be returned by a cache without further validation.</t> 283 283 </list> 284 284 </t> … … 566 566 <t> 567 567 If an origin server wishes to force a cache to validate every request, it 568 can assign an explicit expiration time in the past. This means that the 569 response is always stale, so that caches should validate it before using it 570 for subsequent requests. <cref anchor="TODO-response-stale">This wording 571 might cause confusion, because the response might still be served 572 stale.</cref> 568 can assign an explicit expiration time in the past to indicate that the 569 response is already stale. Compliant caches will validate the cached response 570 before reusing it for subsequent requests. 573 571 </t> 574 572 <t> … … 1741 1739 </t> 1742 1740 <t> 1743 The HTTP Cache Directive Registry sh ouldbe created at <eref1741 The HTTP Cache Directive Registry shall be created at <eref 1744 1742 target="http://www.iana.org/assignments/http-cache-directives"/> and be 1745 1743 populated with the registrations below: … … 1817 1815 The Message Header Field Registry located at <eref 1818 1816 target="http://www.iana.org/assignments/message-headers/message-header-index.html" /> 1819 sh ouldbe updated with the permanent registrations below (see <xref target="RFC3864" />):1817 shall be updated with the permanent registrations below (see <xref target="RFC3864" />): 1820 1818 </t> 1821 1819 <?BEGININC p6-cache.iana-headers ?> … … 1881 1879 on the cache can reveal information long after a user believes that the 1882 1880 information has been removed from the network. Therefore, cache contents 1883 shouldbe protected as sensitive information.1881 need to be protected as sensitive information. 1884 1882 </t> 1885 1883 </section>
Note: See TracChangeset
for help on using the changeset viewer.