Changeset 142
- Timestamp:
- 04/01/08 13:27:42 (15 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r141 r142 904 904 </p> 905 905 <p id="rfc.section.B.1.p.3">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send 906 needed headers in a 206 response, this problem can be avoided. 906 needed headers in a 206 response, this problem can be avoided. (Section <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">3.1</a> and <a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">5.3</a>) 907 907 </p> 908 908 <p id="rfc.section.B.1.p.4">Fix problem with unsatisfiable range requests; there are two cases: syntactic problems, and range doesn't exist in the document. … … 911 911 </p> 912 912 <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 913 <p id="rfc.section.B.2.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206. 1" title="206 Partial Content">Section 3.1</a>)913 <p id="rfc.section.B.2.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section 3.1</a>) 914 914 </p> 915 915 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> Change Log (to be removed by RFC Editor before publication) … … 965 965 <ul class="ind"> 966 966 <li class="indline0"><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul class="ind"> 967 <li class="indline1">206 Partial Content (status code) <a class="iref" href="#rfc.iref.3"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">B. 2</a></li>967 <li class="indline1">206 Partial Content (status code) <a class="iref" href="#rfc.iref.3"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">B.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.2</a></li> 968 968 </ul> 969 969 </li> … … 1012 1012 <li class="indline1">Accept-Ranges <a class="iref" href="#rfc.iref.h.1"><b>5.1</b></a></li> 1013 1013 <li class="indline1">Content-Range <a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a></li> 1014 <li class="indline1">If-Range <a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.iref.h.3"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">5.4.2</a> </li>1014 <li class="indline1">If-Range <a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.iref.h.3"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.3">B.1</a></li> 1015 1015 <li class="indline1">Range <a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>5.4</b></a></li> 1016 1016 </ul> … … 1019 1019 </li> 1020 1020 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> 1021 <li class="indline1">If-Range header <a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.iref.i.1"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">5.4.2</a> </li>1021 <li class="indline1">If-Range header <a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.iref.i.1"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.3">B.1</a></li> 1022 1022 </ul> 1023 1023 </li> … … 1053 1053 <li class="indline1">Status Codes 1054 1054 <ul class="ind"> 1055 <li class="indline1">206 Partial Content <a class="iref" href="#rfc.iref.s.1"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">B. 2</a></li>1055 <li class="indline1">206 Partial Content <a class="iref" href="#rfc.iref.s.1"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">B.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.2</a></li> 1056 1056 <li class="indline1">416 Requested Range Not Satisfiable <a class="iref" href="#rfc.iref.s.2"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">5.2</a>, <a class="iref" href="#rfc.xref.status.416.2">B.1</a></li> 1057 1057 </ul> -
draft-ietf-httpbis/latest/p5-range.xml
r141 r142 1080 1080 were always returned; by allowing the server to only send needed 1081 1081 headers in a 206 response, this problem can be avoided. 1082 (Section <xref target="status.206" format="counter"/> 1083 and <xref target="header.if-range" format="counter"/>) 1082 1084 </t> 1083 1085 <t> -
draft-ietf-httpbis/latest/p6-cache.html
r139 r142 1822 1822 <p id="rfc.section.A.1.p.3">Proxies should be able to add Content-Length when appropriate. (<a href="#non-modifiable.headers" title="Non-modifiable Headers">Section 2.5.2</a>) 1823 1823 </p> 1824 <p id="rfc.section.A.1.p.4">The Cache-Control: max-age directive was not properly defined for responses. (<a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">Section 3.2.3</a>) 1825 </p> 1826 <p id="rfc.section.A.1.p.5">Warnings could be cached incorrectly, or not updated appropriately. (Section <a href="#warnings" title="Warnings">2.1.2</a>, <a href="#expiration.calculations" title="Expiration Calculations">2.2.4</a>, <a href="#non-modifiable.headers" title="Non-modifiable Headers">2.5.2</a>, <a href="#combining.headers" title="Combining Headers">2.5.3</a>, <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">3.2.3</a>, and <a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">3.6</a>) Warning also needed to be a general header, as PUT or other methods may have need for it in requests. 1824 <p id="rfc.section.A.1.p.4">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send 1825 needed headers in a 206 response, this problem can be avoided. (<a href="#combining.headers" title="Combining Headers">Section 2.5.3</a>) 1826 </p> 1827 <p id="rfc.section.A.1.p.5">The Cache-Control: max-age directive was not properly defined for responses. (<a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">Section 3.2.3</a>) 1828 </p> 1829 <p id="rfc.section.A.1.p.6">Warnings could be cached incorrectly, or not updated appropriately. (Section <a href="#warnings" title="Warnings">2.1.2</a>, <a href="#expiration.calculations" title="Expiration Calculations">2.2.4</a>, <a href="#non-modifiable.headers" title="Non-modifiable Headers">2.5.2</a>, <a href="#combining.headers" title="Combining Headers">2.5.3</a>, <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">3.2.3</a>, and <a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">3.6</a>) Warning also needed to be a general header, as PUT or other methods may have need for it in requests. 1827 1830 </p> 1828 1831 <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> -
draft-ietf-httpbis/latest/p6-cache.xml
r139 r142 2835 2835 </t> 2836 2836 <t> 2837 Range request responses would become very verbose if all meta-data 2838 were always returned; by allowing the server to only send needed 2839 headers in a 206 response, this problem can be avoided. 2840 (<xref target="combining.headers"/>) 2841 </t> 2842 <t> 2837 2843 The Cache-Control: max-age directive was not properly defined for 2838 2844 responses. (<xref target="modifications.of.the.basic.expiration.mechanism"/>)
Note: See TracChangeset
for help on using the changeset viewer.