Changeset 1749
- Timestamp:
- 09/07/12 18:04:50 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r1748 r1749 1191 1191 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>. 1192 1192 </p> 1193 <div class="note" id="rfc.section.A.p.2"> 1194 <p> <b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only. 1195 </p> 1196 </div> 1197 <p id="rfc.section.A.p.3">The multipart/byteranges media type includes one or more parts, each with its own <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> and <a href="#header.content-range" class="smpl">Content-Range</a> fields. The required boundary parameter specifies the boundary string used to separate each body-part. 1198 </p> 1199 <p id="rfc.section.A.p.4"> </p> 1193 <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more parts, each with its own <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> and <a href="#header.content-range" class="smpl">Content-Range</a> fields. The required boundary parameter specifies the boundary string used to separate each body-part. 1194 </p> 1195 <p id="rfc.section.A.p.3"> </p> 1200 1196 <dl> 1201 1197 <dt>Type name:</dt> … … 1217 1213 </dd> 1218 1214 <dt>Applications that use this media type:</dt> 1215 <dd>HTTP components supporting multiple ranges in a single request.</dd> 1219 1216 <dt>Additional information:</dt> 1220 1217 <dd> … … 1237 1234 <dd>IESG</dd> 1238 1235 </dl> 1236 <div class="note" id="rfc.section.A.p.4"> 1237 <p> <b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only. 1238 </p> 1239 </div> 1239 1240 <div id="rfc.figure.u.24"></div> 1240 1241 <p>For example:</p><pre class="text"> HTTP/1.1 206 Partial Content … … 1255 1256 --THIS_STRING_SEPARATES-- 1256 1257 </pre><div id="rfc.figure.u.25"></div> 1257 <p> Other example:</p> <pre class="text"> HTTP/1.1 206 Partial Content1258 <p>Another example, using the "exampleunit" range unit:</p> <pre class="text"> HTTP/1.1 206 Partial Content 1258 1259 Date: Tue, 14 Nov 1995 06:25:24 GMT 1259 1260 Last-Modified: Tue, 14 July 04:58:08 GMT -
draft-ietf-httpbis/latest/p5-range.xml
r1748 r1749 1264 1264 "multipart/byteranges". The following is to be registered with IANA <xref target="RFC4288"/>. 1265 1265 </t> 1266 <x:note>1267 <t>1268 &Note; Despite the name "multipart/byteranges" is not limited to the byte ranges only.1269 </t>1270 </x:note>1271 1266 <t> 1272 1267 The multipart/byteranges media type includes one or more parts, each … … 1302 1297 </t> 1303 1298 <t hangText="Applications that use this media type:"> 1299 HTTP components supporting multiple ranges in a single request. 1304 1300 </t> 1305 1301 <t hangText="Additional information:"> … … 1324 1320 </list> 1325 1321 </t> 1322 <x:note> 1323 <t> 1324 &Note; Despite the name "multipart/byteranges" is not limited to the byte ranges only. 1325 </t> 1326 </x:note> 1326 1327 <figure><preamble> 1327 1328 For example: … … 1345 1346 </artwork></figure> 1346 1347 <figure><preamble> 1347 Other example:1348 Another example, using the "exampleunit" range unit: 1348 1349 </preamble> 1349 1350 <artwork type="example"> … … 1367 1368 </figure> 1368 1369 <t> 1369 1370 Notes: 1370 1371 <list style="numbers"> 1371 1372 <t>Additional CRLFs &MAY; precede the first boundary string in the body.</t>
Note: See TracChangeset
for help on using the changeset viewer.