Changeset 932
- Timestamp:
- 24/07/10 14:52:23 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r929 r932 898 898 When a cache receives a 304 (Not Modified) response or a 206 (Partial Content) response 899 899 (in this section, the "new" response"), it needs to created an updated response by combining 900 the stored response with the new one, so that the updated response can be used to satisfy the request. 900 the stored response with the new one, so that the updated response can be used to satisfy 901 the request, and potentially update the cached response. 901 902 </t> 902 903 <t> 903 904 If the new response contains an ETag, it identifies the stored 904 905 response to use. <cref anchor="TODO-mention-CL">might need language about Content-Location 905 here</cref> 906 </t> 907 <t> 908 If the status code is 206 (partial content), both the stored and new906 here</cref><cref anchor="TODO-select-for-combine">Shouldn't this be the selected response?</cref> 907 </t> 908 <t> 909 If the new response's status code is 206 (partial content), both the stored and new 909 910 responses &MUST; have validators, and those validators &MUST; match using the strong 910 911 comparison function (see &weak-and-strong;). Otherwise, the … … 915 916 <list style="symbols"> 916 917 <t>any stored Warning headers with warn-code 1xx (see <xref target="header.warning" />) 917 &MUST; be deleted from the stored response and the updated response.</t> 918 <t>any stored Warning headers with warn-code 2xx &MUST; be retained in the stored 919 response and the updated response.</t> 920 <t>any headers provided in the new response &MUST; replace the corresponding 921 headers from the stored response.</t> 922 </list> 923 </t> 924 <t> 925 If a header field-name in the new response matches more than one 926 header in the stored response, all such stored headers &MUST; be replaced. 927 </t> 928 <t> 929 The updated response can <cref anchor="TODO-is-req">requirement?</cref> be used to replace the 930 stored response in cache. In the case of a 206 response, the combined 931 representation &MAY; be stored. 918 &MUST; be deleted.</t> 919 <t>any stored Warning headers with warn-code 2xx &MUST; be retained.</t> 920 <t>any other headers provided in the new response &MUST; replace all instances of 921 the corresponding headers from the stored response.</t> 922 </list> 923 </t> 924 <t> 925 The updated response headers &MUST; be used to replace those of the 926 stored response in cache (unless the stored response is removed from cache). In the 927 case of a 206 response, the combined representation &MAY; be stored. 932 928 </t> 933 929 </section> … … 2491 2487 "Allowing heuristic caching for new status codes" 2492 2488 </t> 2489 <t> 2490 Clean up TODOs and prose in "Combining Responses." 2491 </t> 2493 2492 </list> 2494 2493 </t>
Note: See TracChangeset
for help on using the changeset viewer.