Changeset 732 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 07/12/09 17:46:53 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r729 r732 495 495 <t> 496 496 Requests with methods that are unsafe (&safe-methods;) &MUST; be written through the cache to 497 the origin server; i.e., Acache must not reply to such a request before having forwarded the request and having received a497 the origin server; i.e., a cache must not reply to such a request before having forwarded the request and having received a 498 498 corresponding response. 499 499 </t> … … 1104 1104 be stored, and cannot ensure the privacy of the message content. 1105 1105 Also, private response directives with field-names are often handled by 1106 implementations as if an unqualified private directive was rec ieved; i.e.,1106 implementations as if an unqualified private directive was received; i.e., 1107 1107 the special handling for the qualified form is not widely implemented. 1108 1108 </t> … … 1345 1345 <t> 1346 1346 Caches use this information, in part, to determine whether a stored response 1347 can be used to satis dy a given request; see1347 can be used to satisfy a given request; see 1348 1348 <xref target="caching.negotiated.responses" />. 1349 1349 determines, while the response is fresh, whether a cache is permitted to use the … … 1403 1403 <t> 1404 1404 Warnings can be used for other purposes, both cache-related and otherwise. The use of a 1405 warning, rather than an error status code, distinguish these responses from true failures.1405 warning, rather than an error status code, distinguishes these responses from true failures. 1406 1406 </t> 1407 1407 <t>
Note: See TracChangeset
for help on using the changeset viewer.