Changeset 1713 for draft-ietf-httpbis/latest/p6-cache.html
- Timestamp:
- 04/07/12 17:59:15 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r1710 r1713 833 833 <p id="rfc.section.2.p.2">Each <dfn>cache entry</dfn> consists of a cache key and one or more HTTP responses corresponding to prior requests that used the same key. The most common 834 834 form of cache entry is a successful result of a retrieval request: i.e., a 200 (OK) response containing a representation of 835 the resource identified by the request target. However, it is also possible to cache negative results (e.g., 404 not found), 836 incomplete results (e.g., 206 partial content), and responses to safe methods other than GET if the method's definition allows 837 such caching and defines something suitable for use as a cache key. 835 the resource identified by the request target. However, it is also possible to cache negative results (e.g., <a href="p2-semantics.html#status.404" class="smpl">404 (Not Found)</a>, incomplete results (e.g., <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a>), and responses to safe methods other than GET if the method's definition allows such caching and defines something suitable 836 for use as a cache key. 838 837 </p> 839 838 <p id="rfc.section.2.p.3">The default <dfn>cache key</dfn> consists of the request method and target URI. However, since HTTP caches in common use today are typically limited to caching
Note: See TracChangeset
for help on using the changeset viewer.