Changeset 911 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 24/07/10 09:23:44 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r908 r911 2138 2138 </references> 2139 2139 2140 <section anchor="compatibility" title="Compatibility with Previous Versions">2141 2142 <section anchor="changes.from.rfc.2068" title="Changes from RFC 2068">2143 <t>2144 A case was missed in the Cache-Control model of HTTP/1.1; s-maxage was introduced to add2145 this missing case.2146 (Sections <xref format="counter" target="response.cacheability" />, <xref format="counter" target="header.cache-control" />).2147 </t>2148 <t>2149 Range request responses would become very verbose if all meta-data were always returned;2150 by allowing the server to only send needed headers in a 206 response, this problem can be2151 avoided.2152 (<xref target="combining.headers" />)2153 </t>2154 <t>2155 The Cache-Control: max-age directive was not properly defined for responses.2156 (<xref target="cache-response-directive"/>)2157 </t>2158 <t>2159 Warnings could be cached incorrectly, or not updated appropriately. (Section <xref2160 format="counter" target="expiration.model" />, <xref format="counter"2161 target="combining.headers" />, <xref format="counter" target="header.cache-control" />,2162 and <xref format="counter" target="header.warning" />) Warning also needed to be a general2163 header, as PUT or other methods may have need for it in requests.2164 </t>2165 </section>2166 2167 2140 <section anchor="changes.from.rfc.2616" title="Changes from RFC 2616"> 2168 2141 <t> … … 2185 2158 </t> 2186 2159 </section> 2187 2188 </section>2189 2160 2190 2161 <?BEGININC p6-cache.abnf-appendix ?> … … 2507 2478 <section title="Since draft-ietf-httpbis-p6-cache-10" anchor="changes.since.10"> 2508 2479 <t> 2509 None yet. 2480 Closed issues: 2481 <list style="symbols"> 2482 <t> 2483 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/220"/>: 2484 "consider removing the 'changes from 2068' sections" 2485 </t> 2486 </list> 2510 2487 </t> 2511 2488 </section>
Note: See TracChangeset
for help on using the changeset viewer.