Changeset 395 for draft-ietf-httpbis/latest/p6-cache.html
- Timestamp:
- 15/11/08 07:49:55 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r391 r395 485 485 <tr> 486 486 <td class="header left"></td> 487 <td class="header right">November 1 5, 2008</td>487 <td class="header right">November 14, 2008</td> 488 488 </tr> 489 489 </table> … … 1089 1089 <p id="rfc.section.7.3.p.2">If the status code is 304 (Not Modified), the cache uses the entity-body stored in the cache entry as the entity-body of this 1090 1090 outgoing response. If the status code is 206 (Partial Content) and the ETag or Last-Modified headers match exactly, the cache <em class="bcp14">MAY</em> combine the contents stored in the cache entry with the new contents received in the response and use the result as the entity-body 1091 of this outgoing response, (see <a href="p5-range.html#combining.byte.ranges" title="Combining ByteRanges">Section 5</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>).1091 of this outgoing response, (see <a href="p5-range.html#combining.byte.ranges" title="Combining Ranges">Section 5</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>). 1092 1092 </p> 1093 1093 <p id="rfc.section.7.3.p.3">The end-to-end headers stored in the cache entry are used for the constructed response, except that </p> … … 1156 1156 </p> 1157 1157 <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a> <a id="errors.or.incomplete.response.cache.behavior" href="#errors.or.incomplete.response.cache.behavior">Errors or Incomplete Response Cache Behavior</a></h1> 1158 <p id="rfc.section.10.p.1">A cache that receives an incomplete response (for example, with fewer bytes of data than specified in a Content-Length header) <em class="bcp14">MAY</em> store the response. However, the cache <em class="bcp14">MUST</em> treat this as a partial response. Partial responses <em class="bcp14">MAY</em> be combined as described in <a href="p5-range.html#combining.byte.ranges" title="Combining ByteRanges">Section 5</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>; the result might be a full response or might still be partial. A cache <em class="bcp14">MUST NOT</em> return a partial response to a client without explicitly marking it as such, using the 206 (Partial Content) status code.1158 <p id="rfc.section.10.p.1">A cache that receives an incomplete response (for example, with fewer bytes of data than specified in a Content-Length header) <em class="bcp14">MAY</em> store the response. However, the cache <em class="bcp14">MUST</em> treat this as a partial response. Partial responses <em class="bcp14">MAY</em> be combined as described in <a href="p5-range.html#combining.byte.ranges" title="Combining Ranges">Section 5</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>; the result might be a full response or might still be partial. A cache <em class="bcp14">MUST NOT</em> return a partial response to a client without explicitly marking it as such, using the 206 (Partial Content) status code. 1159 1159 A cache <em class="bcp14">MUST NOT</em> return a partial response using a status code of 200 (OK). 1160 1160 </p> … … 1951 1951 <p id="rfc.section.B.2.p.2">Other changes: </p> 1952 1952 <ul> 1953 <li>Use names of RFC4234 core rule s DQUOTE and HTAB(work in progress on <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>)1953 <li>Use names of RFC4234 core rule DQUOTE (work in progress on <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>) 1954 1954 </li> 1955 1955 </ul>
Note: See TracChangeset
for help on using the changeset viewer.