Changeset 332 for draft-ietf-httpbis
- Timestamp:
- 02/11/08 16:32:36 (14 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r331 r332 473 473 <tr> 474 474 <td class="header left"></td> 475 <td class="header right">November 1, 2008</td>475 <td class="header right">November 2, 2008</td> 476 476 </tr> 477 477 </table> … … 971 971 non-overlapping ranges), these are transmitted as a multipart message-body (<a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="http://tools.ietf.org/html/rfc2046#section-5.1">Section 5.1</a>). The media type for this purpose is called "multipart/byteranges". The following is to be registered with IANA <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>. 972 972 </p> 973 <p id="rfc.section.A.p.2">The multipart/byteranges media type includes twoor more parts, each with its own Content-Type and Content-Range fields. The973 <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more parts, each with its own Content-Type and Content-Range fields. The 974 974 required boundary parameter specifies the boundary string used to separate each body-part. 975 975 </p> … … 1059 1059 <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 4.1</a>) 1060 1060 </p> 1061 <p id="rfc.section.B.2.p.2">Clarify that multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>) 1062 </p> 1061 1063 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 1062 1064 <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a> Since RFC2616 … … 1095 1097 <h2 id="rfc.section.C.5"><a href="#rfc.section.C.5">C.5</a> <a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></h2> 1096 1098 <h2 id="rfc.section.C.6"><a href="#rfc.section.C.6">C.6</a> <a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></h2> 1099 <p id="rfc.section.C.6.p.1">Closed issues: </p> 1100 <ul> 1101 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/133">http://tools.ietf.org/wg/httpbis/trac/ticket/133</a>>: "multipart/byteranges minimum number of parts" 1102 </li> 1103 </ul> 1097 1104 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 1098 1105 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the -
draft-ietf-httpbis/latest/p5-range.xml
r331 r332 1157 1157 "multipart/byteranges". The following is to be registered with IANA <xref target="RFC4288"/>. 1158 1158 </t><t> 1159 The multipart/byteranges media type includes twoor more parts, each1159 The multipart/byteranges media type includes one or more parts, each 1160 1160 with its own Content-Type and Content-Range fields. The required 1161 1161 boundary parameter specifies the boundary string used to separate … … 1287 1287 (<xref target="status.206"/>) 1288 1288 </t> 1289 <t> 1290 Clarify that multipart/byteranges can consist of a single part. 1291 (<xref target="internet.media.type.multipart.byteranges"/>) 1292 </t> 1293 1289 1294 </section> 1290 1295 … … 1359 1364 <section title="Since draft-ietf-httpbis-p5-range-04" anchor="changes.since.04"> 1360 1365 <t> 1366 Closed issues: 1367 <list style="symbols"> 1368 <t> 1369 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/133"/>: 1370 "multipart/byteranges minimum number of parts" 1371 </t> 1372 </list> 1361 1373 </t> 1362 1374 </section>
Note: See TracChangeset
for help on using the changeset viewer.