Changeset 1715 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 04/07/12 19:54:55 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r1713 r1715 432 432 HTTP responses corresponding to prior requests that used the same key. 433 433 The most common form of cache entry is a successful result of a retrieval 434 request: i.e., a 200 (OK) response containing a representation of the435 resource identified by the request target. However, it is also possible434 request: i.e., a <x:ref>200 (OK)</x:ref> response containing a representation 435 of the resource identified by the request target. However, it is also possible 436 436 to cache negative results (e.g., <x:ref>404 (Not Found)</x:ref>, incomplete results 437 437 (e.g., <x:ref>206 (Partial Content)</x:ref>), and responses to safe methods other than … … 504 504 A response message is considered complete when all of the octets 505 505 indicated by the message framing (&messaging;) are received 506 prior to the connection being closed. 507 If the request is GET, the response status is 200 (OK), and the entire506 prior to the connection being closed. If the request is GET, the response 507 status is <x:ref>200 (OK)</x:ref>, and the entire 508 508 response header block has been received, a cache &MAY; store an incomplete 509 509 response message body if the cache entry is recorded as incomplete. 510 510 Likewise, a <x:ref>206 (Partial Content)</x:ref> response &MAY; be stored as if it were 511 an incomplete 200 (OK)cache entry. However, a cache &MUST-NOT; store511 an incomplete <x:ref>200 (OK)</x:ref> cache entry. However, a cache &MUST-NOT; store 512 512 incomplete or partial content responses if it does not support the Range 513 513 and Content-Range header fields or if it does not understand the … … 929 929 <t> 930 930 When a cache receives a <x:ref>304 (Not Modified)</x:ref> response and already has one 931 or more stored 200 (OK)responses for the same cache key, the cache needs931 or more stored <x:ref>200 (OK)</x:ref> responses for the same cache key, the cache needs 932 932 to identify which of the stored responses are updated by this new response 933 933 and then update the stored response(s) with the new information provided in … … 2288 2288 <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;" /> 2289 2289 <x:source basename="p2-semantics" href="p2-semantics.xml"> 2290 <x:defines>200 (OK)</x:defines> 2290 2291 <x:defines>404 (Not Found)</x:defines> 2291 2292 <x:defines>504 (Gateway Timeout)</x:defines>
Note: See TracChangeset
for help on using the changeset viewer.