You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@labs.apache.org by fi...@apache.org on 2007/10/10 01:56:03 UTC
svn commit: r583326 [6/14] - /labs/webarch/trunk/http/draft-fielding-http/
Modified: labs/webarch/trunk/http/draft-fielding-http/p5-range.html
URL: http://svn.apache.org/viewvc/labs/webarch/trunk/http/draft-fielding-http/p5-range.html?rev=583326&r1=583325&r2=583326&view=diff
==============================================================================
--- labs/webarch/trunk/http/draft-fielding-http/p5-range.html (original)
+++ labs/webarch/trunk/http/draft-fielding-http/p5-range.html Tue Oct 9 16:56:02 2007
@@ -1,6 +1,9 @@
<!DOCTYPE html
PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en"><head profile="http://www.w3.org/2006/03/hcard"><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><title>HTTP/1.1, part 5: Range Requests and Partial Responses</title><style type="text/css" title="Xml2Rfc (sans serif)">
+<html lang="en">
+ <head profile="http://www.w3.org/2006/03/hcard">
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <title>HTTP/1.1, part 5: Range Requests and Partial Responses</title><style type="text/css" title="Xml2Rfc (sans serif)">
a {
text-decoration: none;
}
@@ -324,18 +327,250 @@
content: normal;
}
}
-</style><link rel="Contents" href="#rfc.toc"><link rel="Author" href="#rfc.authors"><link rel="Copyright" href="#rfc.copyright"><link rel="Index" href="#rfc.index"><link rel="Chapter" title="1 Introduction" href="#rfc.section.1"><link rel="Chapter" title="2 Range Units" href="#rfc.section.2"><link rel="Chapter" title="3 206 Partial Content" href="#rfc.section.3"><link rel="Chapter" title="4 416 Requested Range Not Satisfiable" href="#rfc.section.4"><link rel="Chapter" title="5 Combining Byte Ranges" href="#rfc.section.5"><link rel="Chapter" title="6 Header Field Definitions" href="#rfc.section.6"><link rel="Chapter" title="7 Acknowledgments" href="#rfc.section.7"><link rel="Chapter" title="8 Security Considerations" href="#rfc.section.8"><link rel="Chapter" href="#rfc.section.9" title="9 References"><link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A"><link rel="Appendix" title="B Changes from RFC 2068" href="#rfc.section.B"><meta nam
e="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.346, 2007/10/07 13:54:24, XSLT vendor: SAXON 8.5.1 from Saxonica http://www.saxonica.com/"><link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"><meta name="DC.Creator" content="Fielding, R."><meta name="DC.Creator" content="Gettys, J."><meta name="DC.Creator" content="Mogul, J."><meta name="DC.Creator" content="Frystyk, H."><meta name="DC.Creator" content="Masinter, L."><meta name="DC.Creator" content="Leach, P."><meta name="DC.Creator" content="Berners-Lee, T."><meta name="DC.Identifier" content="urn:ietf:id:draft-fielding-http-p5-range-00"><meta name="DC.Date.Issued" scheme="ISO8601" content="2007-09"><meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2068"><meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"><meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2617"><meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application
-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the eight-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, updates RFC 2616 and RFC 2617. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."></head><body><table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1"><tr><td class="header left">Network Working Group</td><td class="header right">R. Fielding</td></tr><tr><td class="header left">Internet Draft</td><td class="header right">UC Irvine</td></tr><tr><td class="header left">
- <draft-fielding-http-p5-range-00>
- </td><td class="header right">J. Gettys</td></tr><tr><td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a>,
- <a href="http://tools.ietf.org/html/rfc2616">2616</a>,
- <a href="http://tools.ietf.org/html/rfc2617">2617</a> (if approved)</td><td class="header right">Compaq/W3C</td></tr><tr><td class="header left">Intended status: Standards Track</td><td class="header right">J. Mogul</td></tr><tr><td class="header left">Expires: March 2008</td><td class="header right">Compaq</td></tr><tr><td class="header left"></td><td class="header right">H. Frystyk</td></tr><tr><td class="header left"></td><td class="header right">W3C/MIT</td></tr><tr><td class="header left"></td><td class="header right">L. Masinter</td></tr><tr><td class="header left"></td><td class="header right">Xerox</td></tr><tr><td class="header left"></td><td class="header right">P. Leach</td></tr><tr><td class="header left"></td><td class="header right">Microsoft</td></tr><tr><td class="header left"></td><td class="header right">T. Berners-Lee</td></tr><tr><td class="header left"></td><td class="header right">W3C/MIT</td></tr><tr><td class="header left"></td><td class="header
right">September 2007</td></tr></table><p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-fielding-http-p5-range-00</span></p><h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1><p>This document is an Internet-Draft and is subject to all provisions of section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she become aware will be disclosed, in accordance with RFC 3668.</p><p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.</p><p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Inte
rnet-Drafts as reference material or to cite them other than as “work in progress”.</p><p>The list of current Internet-Drafts can be accessed at <<a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>>.</p><p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>.</p><p>This Internet-Draft will expire in March 2008.</p><h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1><p>Copyright © The IETF Trust (2007). All Rights Reserved.</p><h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the eight-part specification that defines the
protocol referred to as "HTTP/1.1" and, taken together, updates RFC 2616 and RFC 2617. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.</p> <hr class="noprint"><h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1><ul class="toc"><li class="tocline0">1. <a href="#rfc.section.1">Introduction</a></li><li class="tocline0">2. <a href="#range.units">Range Units</a></li><li class="tocline0">3. <a href="#status.206">206 Partial Content</a></li><li class="tocline0">4. <a href="#status.416">416 Requested Range Not Satisfiable</a></li><li class="tocline0">5. <a href="#combining.byte.ranges">Combining Byte Ranges</a></li><li class="tocline0">6. <a href="#rfc.section.6">Header Field Definitions</a><ul class="toc"><li class="tocline1">6.1 <a href="#header.accept-ranges">Accept-Ranges</a></
li><li class="tocline1">6.2 <a href="#header.content-range">Content-Range</a></li><li class="tocline1">6.3 <a href="#header.if-range">If-Range</a></li><li class="tocline1">6.4 <a href="#header.range">Range</a><ul class="toc"><li class="tocline1">6.4.1 <a href="#byte.ranges">Byte Ranges</a></li><li class="tocline1">6.4.2 <a href="#rfc.section.6.4.2">Range Retrieval Requests</a></li></ul></li></ul></li><li class="tocline0">7. <a href="#rfc.section.7">Acknowledgments</a></li><li class="tocline0">8. <a href="#rfc.section.8">Security Considerations</a></li><li class="tocline0">9. <a href="#rfc.references">References</a></li><li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li><li class="tocline0">A. <a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li><li class="to
cline0">B. <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li><li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li><li class="tocline0"><a href="#rfc.index">Index</a></li></ul><h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> Introduction</h1><p id="rfc.section.1.p.1">This document will define aspects of HTTP related to range requests, partial responses, and the multipart/byteranges media type. Right now it only includes the extracted relevant sections of <a href="#RFC2616">RFC 2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">[2]</cite> without edit.</p><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="range.units" href="#range.units">Range Units</a></h1><p id="rfc.section.2.p.1">HTTP/1.1 allows a client to request that only part (a range of) the response entity be included within the response. HTTP/1.1 uses range units in the Ran
ge (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section 6.4</a>) and Content-Range (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section 6.2</a>) header fields. An entity can be broken down into subranges according to various structural units.</p><div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span> range-unit = bytes-unit | other-range-unit
+</style><link rel="Contents" href="#rfc.toc">
+ <link rel="Author" href="#rfc.authors">
+ <link rel="Copyright" href="#rfc.copyright">
+ <link rel="Index" href="#rfc.index">
+ <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
+ <link rel="Chapter" title="2 Range Units" href="#rfc.section.2">
+ <link rel="Chapter" title="3 206 Partial Content" href="#rfc.section.3">
+ <link rel="Chapter" title="4 416 Requested Range Not Satisfiable" href="#rfc.section.4">
+ <link rel="Chapter" title="5 Combining Byte Ranges" href="#rfc.section.5">
+ <link rel="Chapter" title="6 Header Field Definitions" href="#rfc.section.6">
+ <link rel="Chapter" title="7 Acknowledgments" href="#rfc.section.7">
+ <link rel="Chapter" title="8 Security Considerations" href="#rfc.section.8">
+ <link rel="Chapter" href="#rfc.section.9" title="9 References">
+ <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A">
+ <link rel="Appendix" title="B Changes from RFC 2068" href="#rfc.section.B">
+ <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.346, 2007/10/07 13:54:24, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
+ <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
+ <meta name="DC.Creator" content="Fielding, R.">
+ <meta name="DC.Creator" content="Gettys, J.">
+ <meta name="DC.Creator" content="Mogul, J.">
+ <meta name="DC.Creator" content="Frystyk, H.">
+ <meta name="DC.Creator" content="Masinter, L.">
+ <meta name="DC.Creator" content="Leach, P.">
+ <meta name="DC.Creator" content="Berners-Lee, T.">
+ <meta name="DC.Identifier" content="urn:ietf:id:draft-fielding-http-p5-range-00">
+ <meta name="DC.Date.Issued" scheme="ISO8601" content="2007-09">
+ <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2068">
+ <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
+ <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2617">
+ <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the eight-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, updates RFC 2616 and RFC 2617. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.">
+ </head>
+ <body>
+ <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1">
+ <tr>
+ <td class="header left">Network Working Group</td>
+ <td class="header right">R. Fielding</td>
+ </tr>
+ <tr>
+ <td class="header left">Internet Draft</td>
+ <td class="header right">UC Irvine</td>
+ </tr>
+ <tr>
+ <td class="header left">
+ <draft-fielding-http-p5-range-00>
+
+ </td>
+ <td class="header right">J. Gettys</td>
+ </tr>
+ <tr>
+ <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a>,
+ <a href="http://tools.ietf.org/html/rfc2616">2616</a>,
+ <a href="http://tools.ietf.org/html/rfc2617">2617</a> (if approved)
+ </td>
+ <td class="header right">Compaq/W3C</td>
+ </tr>
+ <tr>
+ <td class="header left">Intended status: Standards Track</td>
+ <td class="header right">J. Mogul</td>
+ </tr>
+ <tr>
+ <td class="header left">Expires: March 2008</td>
+ <td class="header right">Compaq</td>
+ </tr>
+ <tr>
+ <td class="header left"></td>
+ <td class="header right">H. Frystyk</td>
+ </tr>
+ <tr>
+ <td class="header left"></td>
+ <td class="header right">W3C/MIT</td>
+ </tr>
+ <tr>
+ <td class="header left"></td>
+ <td class="header right">L. Masinter</td>
+ </tr>
+ <tr>
+ <td class="header left"></td>
+ <td class="header right">Xerox</td>
+ </tr>
+ <tr>
+ <td class="header left"></td>
+ <td class="header right">P. Leach</td>
+ </tr>
+ <tr>
+ <td class="header left"></td>
+ <td class="header right">Microsoft</td>
+ </tr>
+ <tr>
+ <td class="header left"></td>
+ <td class="header right">T. Berners-Lee</td>
+ </tr>
+ <tr>
+ <td class="header left"></td>
+ <td class="header right">W3C/MIT</td>
+ </tr>
+ <tr>
+ <td class="header left"></td>
+ <td class="header right">September 2007</td>
+ </tr>
+ </table>
+ <p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-fielding-http-p5-range-00</span></p>
+ <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
+ <p>This document is an Internet-Draft and is subject to all provisions of section 3 of RFC 3667. By submitting this Internet-Draft,
+ each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed,
+ and any of which he or she become aware will be disclosed, in accordance with RFC 3668.
+ </p>
+ <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
+ that other groups may also distribute working documents as Internet-Drafts.
+ </p>
+ <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
+ documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as âwork
+ in progressâ.
+ </p>
+ <p>The list of current Internet-Drafts can be accessed at <<a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>>.
+ </p>
+ <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>.
+ </p>
+ <p>This Internet-Draft will expire in March 2008.</p>
+ <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
+ <p>Copyright © The IETF Trust (2007). All Rights Reserved.</p>
+ <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
+ <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
+ systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the
+ eight-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, updates RFC 2616 and RFC
+ 2617. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.
+ </p>
+ <hr class="noprint">
+ <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
+ <ul class="toc">
+ <li class="tocline0">1. <a href="#rfc.section.1">Introduction</a></li>
+ <li class="tocline0">2. <a href="#range.units">Range Units</a></li>
+ <li class="tocline0">3. <a href="#status.206">206 Partial Content</a></li>
+ <li class="tocline0">4. <a href="#status.416">416 Requested Range Not Satisfiable</a></li>
+ <li class="tocline0">5. <a href="#combining.byte.ranges">Combining Byte Ranges</a></li>
+ <li class="tocline0">6. <a href="#rfc.section.6">Header Field Definitions</a><ul class="toc">
+ <li class="tocline1">6.1 <a href="#header.accept-ranges">Accept-Ranges</a></li>
+ <li class="tocline1">6.2 <a href="#header.content-range">Content-Range</a></li>
+ <li class="tocline1">6.3 <a href="#header.if-range">If-Range</a></li>
+ <li class="tocline1">6.4 <a href="#header.range">Range</a><ul class="toc">
+ <li class="tocline1">6.4.1 <a href="#byte.ranges">Byte Ranges</a></li>
+ <li class="tocline1">6.4.2 <a href="#rfc.section.6.4.2">Range Retrieval Requests</a></li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+ <li class="tocline0">7. <a href="#rfc.section.7">Acknowledgments</a></li>
+ <li class="tocline0">8. <a href="#rfc.section.8">Security Considerations</a></li>
+ <li class="tocline0">9. <a href="#rfc.references">References</a></li>
+ <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
+ <li class="tocline0">A. <a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li>
+ <li class="tocline0">B. <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
+ <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
+ <li class="tocline0"><a href="#rfc.index">Index</a></li>
+ </ul>
+ <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> Introduction
+ </h1>
+ <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to range requests, partial responses, and the multipart/byteranges media
+ type. Right now it only includes the extracted relevant sections of <a href="#RFC2616">RFC 2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">[2]</cite> without edit.
+ </p>
+ <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="range.units" href="#range.units">Range Units</a></h1>
+ <p id="rfc.section.2.p.1">HTTP/1.1 allows a client to request that only part (a range of) the response entity be included within the response. HTTP/1.1
+ uses range units in the Range (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section 6.4</a>) and Content-Range (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section 6.2</a>) header fields. An entity can be broken down into subranges according to various structural units.
+ </p>
+ <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span> range-unit = bytes-unit | other-range-unit
bytes-unit = "bytes"
other-range-unit = token
-</pre><p id="rfc.section.2.p.3">The only range unit defined by HTTP/1.1 is "bytes". HTTP/1.1 implementations <em class="bcp14">MAY</em> ignore ranges specified using other units.</p><p id="rfc.section.2.p.4">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges.</p><div id="rfc.iref.3"></div><div id="rfc.iref.s.1"></div><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="status.206" href="#status.206">206 Partial Content</a></h1><p id="rfc.section.3.p.1">The server has fulfilled the partial GET request for the resource. The request <em class="bcp14">MUST</em> have included a Range header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section 6.4</a>) indicating the desired range, and <em class="bcp14">MAY</em> have included an If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section 6.3</a>) to make the request conditio
nal.</p><p id="rfc.section.3.p.2">The response <em class="bcp14">MUST</em> include the following header fields: </p><ul><li>Either a Content-Range header field (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section 6.2</a>) indicating the range included with this response, or a multipart/byteranges Content-Type including Content-Range fields for each part. If a Content-Length header field is present in the response, its value <em class="bcp14">MUST</em> match the actual number of OCTETs transmitted in the message-body.</li><li>Date</li><li>ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request</li><li>Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same variant</li></ul><p id="rfc.section.3.p.3">If the 206 response is the result of an If-Range request that used a strong cache validator (see [Part 4]), the respo
nse <em class="bcp14">SHOULD NOT</em> include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response <em class="bcp14">MUST NOT</em> include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the response <em class="bcp14">MUST</em> include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.</p><p id="rfc.section.3.p.4">A cache <em class="bcp14">MUST NOT</em> combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly, see <a href="#combining.byte.ranges" title="Combining Byte Ranges">5</a>.</p><p id="rfc.section.3.p.5">A cache that does not support the Range and Content-Range headers <em class="bcp14">MUST NOT</em> cache 206 (Partial) responses.</p><div id="rfc.iref.4"></div><div id="rfc.iref.s.2"></div><h1 id="rfc.section.4"><a href="#rfc.section
.4">4.</a> <a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h1><p id="rfc.section.4.p.1">A server <em class="bcp14">SHOULD</em> return a response with this status code if a request included a Range request-header field (<a href="#header.range" id="rfc.xref.header.range.3" title="Range">Section 6.4</a>), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec values were greater than the current length of the selected resource.)</p><p id="rfc.section.4.p.2">When this status code is returned for a byte-range request, the response <em class="bcp14">SHOULD</em> include a Content-Range entity-header field specifying the current length of the selected resource (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Conten
t-Range">Section 6.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type.</p><h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Byte Ranges</a></h1><p id="rfc.section.5.p.1">A response might transfer only a subrange of the bytes of an entity-body, either because the request included one or more Range specifications, or because a connection was broken prematurely. After several such transfers, a cache might have received several ranges of the same entity-body.</p><p id="rfc.section.5.p.2">If a cache has a stored non-empty set of subranges for an entity, and an incoming response transfers another subrange, the cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met: </p><ul><li>Both the incoming response and the cache entry have a cache validator.</li><li>The two cache validators match usi
ng the strong comparison function (see [Part 4]).</li></ul><p id="rfc.section.5.p.3">If either requirement is not met, the cache <em class="bcp14">MUST</em> use only the most recent partial response (based on the Date values transmitted with every response, and using the incoming response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information.</p><h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> Header Field Definitions</h1><p id="rfc.section.6.p.1">This section defines the syntax and semantics of all standard HTTP/1.1 header fields. For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who receives the entity.</p><div id="rfc.iref.a.1"></div><div id="rfc.iref.h.1"></div><h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a> <a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2><p id="rfc.section.6.1.p.1">The A
ccept-Ranges response-header field allows the server to indicate its acceptance of range requests for a resource:</p><div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span> Accept-Ranges = "Accept-Ranges" ":" acceptable-ranges
+</pre><p id="rfc.section.2.p.3">The only range unit defined by HTTP/1.1 is "bytes". HTTP/1.1 implementations <em class="bcp14">MAY</em> ignore ranges specified using other units.
+ </p>
+ <p id="rfc.section.2.p.4">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges.</p>
+ <div id="rfc.iref.3"></div>
+ <div id="rfc.iref.s.1"></div>
+ <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="status.206" href="#status.206">206 Partial Content</a></h1>
+ <p id="rfc.section.3.p.1">The server has fulfilled the partial GET request for the resource. The request <em class="bcp14">MUST</em> have included a Range header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section 6.4</a>) indicating the desired range, and <em class="bcp14">MAY</em> have included an If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section 6.3</a>) to make the request conditional.
+ </p>
+ <p id="rfc.section.3.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
+ </p>
+ <ul>
+ <li>Either a Content-Range header field (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section 6.2</a>) indicating the range included with this response, or a multipart/byteranges Content-Type including Content-Range fields
+ for each part. If a Content-Length header field is present in the response, its value <em class="bcp14">MUST</em> match the actual number of OCTETs transmitted in the message-body.
+ </li>
+ <li>Date</li>
+ <li>ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request</li>
+ <li>Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same
+ variant
+ </li>
+ </ul>
+ <p id="rfc.section.3.p.3">If the 206 response is the result of an If-Range request that used a strong cache validator (see [Part 4]), the response <em class="bcp14">SHOULD NOT</em> include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response <em class="bcp14">MUST NOT</em> include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the
+ response <em class="bcp14">MUST</em> include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.
+ </p>
+ <p id="rfc.section.3.p.4">A cache <em class="bcp14">MUST NOT</em> combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly, see <a href="#combining.byte.ranges" title="Combining Byte Ranges">5</a>.
+ </p>
+ <p id="rfc.section.3.p.5">A cache that does not support the Range and Content-Range headers <em class="bcp14">MUST NOT</em> cache 206 (Partial) responses.
+ </p>
+ <div id="rfc.iref.4"></div>
+ <div id="rfc.iref.s.2"></div>
+ <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h1>
+ <p id="rfc.section.4.p.1">A server <em class="bcp14">SHOULD</em> return a response with this status code if a request included a Range request-header field (<a href="#header.range" id="rfc.xref.header.range.3" title="Range">Section 6.4</a>), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request
+ did not include an If-Range request-header field. (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec
+ values were greater than the current length of the selected resource.)
+ </p>
+ <p id="rfc.section.4.p.2">When this status code is returned for a byte-range request, the response <em class="bcp14">SHOULD</em> include a Content-Range entity-header field specifying the current length of the selected resource (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section 6.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type.
+ </p>
+ <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Byte Ranges</a></h1>
+ <p id="rfc.section.5.p.1">A response might transfer only a subrange of the bytes of an entity-body, either because the request included one or more
+ Range specifications, or because a connection was broken prematurely. After several such transfers, a cache might have received
+ several ranges of the same entity-body.
+ </p>
+ <p id="rfc.section.5.p.2">If a cache has a stored non-empty set of subranges for an entity, and an incoming response transfers another subrange, the
+ cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met:
+ </p>
+ <ul>
+ <li>Both the incoming response and the cache entry have a cache validator.</li>
+ <li>The two cache validators match using the strong comparison function (see [Part 4]).</li>
+ </ul>
+ <p id="rfc.section.5.p.3">If either requirement is not met, the cache <em class="bcp14">MUST</em> use only the most recent partial response (based on the Date values transmitted with every response, and using the incoming
+ response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information.
+ </p>
+ <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> Header Field Definitions
+ </h1>
+ <p id="rfc.section.6.p.1">This section defines the syntax and semantics of all standard HTTP/1.1 header fields. For entity-header fields, both sender
+ and recipient refer to either the client or the server, depending on who sends and who receives the entity.
+ </p>
+ <div id="rfc.iref.a.1"></div>
+ <div id="rfc.iref.h.1"></div>
+ <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a> <a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2>
+ <p id="rfc.section.6.1.p.1">The Accept-Ranges response-header field allows the server to indicate its acceptance of range requests for a resource:</p>
+ <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span> Accept-Ranges = "Accept-Ranges" ":" acceptable-ranges
acceptable-ranges = 1#range-unit | "none"
-</pre><p id="rfc.section.6.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send</p><div id="rfc.figure.u.3"></div><pre class="text"> Accept-Ranges: bytes
-</pre><p id="rfc.section.6.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate byte-range requests without having received this header for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section 2</a>.</p><p id="rfc.section.6.1.p.6">Servers that do not accept any kind of range request for a resource <em class="bcp14">MAY</em> send</p><div id="rfc.figure.u.4"></div><pre class="text"> Accept-Ranges: none
-</pre><p id="rfc.section.6.1.p.8">to advise the client not to attempt a range request.</p><div id="rfc.iref.c.1"></div><div id="rfc.iref.h.2"></div><h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a> <a id="header.content-range" href="#header.content-range">Content-Range</a></h2><p id="rfc.section.6.2.p.1">The Content-Range entity-header is sent with a partial entity-body to specify where in the full entity-body the partial body should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section 2</a>.</p><div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> Content-Range = "Content-Range" ":" content-range-spec
+</pre><p id="rfc.section.6.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
+ </p>
+ <div id="rfc.figure.u.3"></div><pre class="text"> Accept-Ranges: bytes
+</pre><p id="rfc.section.6.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate byte-range requests without having received this header for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section 2</a>.
+ </p>
+ <p id="rfc.section.6.1.p.6">Servers that do not accept any kind of range request for a resource <em class="bcp14">MAY</em> send
+ </p>
+ <div id="rfc.figure.u.4"></div><pre class="text"> Accept-Ranges: none
+</pre><p id="rfc.section.6.1.p.8">to advise the client not to attempt a range request.</p>
+ <div id="rfc.iref.c.1"></div>
+ <div id="rfc.iref.h.2"></div>
+ <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a> <a id="header.content-range" href="#header.content-range">Content-Range</a></h2>
+ <p id="rfc.section.6.2.p.1">The Content-Range entity-header is sent with a partial entity-body to specify where in the full entity-body the partial body
+ should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section 2</a>.
+ </p>
+ <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> Content-Range = "Content-Range" ":" content-range-spec
content-range-spec = byte-content-range-spec
byte-content-range-spec = bytes-unit SP
@@ -345,27 +580,209 @@
byte-range-resp-spec = (first-byte-pos "-" last-byte-pos)
| "*"
instance-length = 1*DIGIT
-</pre><p id="rfc.section.6.2.p.3">The header <em class="bcp14">SHOULD</em> indicate the total length of the full entity-body, unless this length is unknown or difficult to determine. The asterisk "*" character means that the instance-length is unknown at the time when the response was generated.</p><p id="rfc.section.6.2.p.4">Unlike byte-ranges-specifier values (see <a href="#byte.ranges" title="Byte Ranges">Section 6.4.1</a>), a byte-range-resp-spec <em class="bcp14">MUST</em> only specify one range, and <em class="bcp14">MUST</em> contain absolute byte positions for both the first and last byte of the range.</p><p id="rfc.section.6.2.p.5">A byte-content-range-spec with a byte-range-resp-spec whose last-byte-pos value is less than its first-byte-pos value, or whose instance-length value is less than or equal to its last-byte-pos value, is invalid. The recipient of an invalid byte-content-range-spec <em class="bcp14">MUST</em> ignore it and any content transferred along
with it.</p><p id="rfc.section.6.2.p.6">A server sending a response with status code 416 (Requested range not satisfiable) <em class="bcp14">SHOULD</em> include a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the selected resource. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".</p><p id="rfc.section.6.2.p.7">Examples of byte-content-range-spec values, assuming that the entity contains a total of 1234 bytes: </p><ul><li>The first 500 bytes: <div id="rfc.figure.u.6"></div><pre class="text"> bytes 0-499/1234
-</pre> </li><li>The second 500 bytes: <div id="rfc.figure.u.7"></div><pre class="text"> bytes 500-999/1234
-</pre> </li><li>All except for the first 500 bytes: <div id="rfc.figure.u.8"></div><pre class="text"> bytes 500-1233/1234
-</pre> </li><li>The last 500 bytes: <div id="rfc.figure.u.9"></div><pre class="text"> bytes 734-1233/1234
-</pre> </li></ul><p id="rfc.section.6.2.p.8">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header, and a Content-Length header showing the number of bytes actually transferred. For example,</p><div id="rfc.figure.u.10"></div><pre class="text"> HTTP/1.1 206 Partial content
+</pre><p id="rfc.section.6.2.p.3">The header <em class="bcp14">SHOULD</em> indicate the total length of the full entity-body, unless this length is unknown or difficult to determine. The asterisk "*"
+ character means that the instance-length is unknown at the time when the response was generated.
+ </p>
+ <p id="rfc.section.6.2.p.4">Unlike byte-ranges-specifier values (see <a href="#byte.ranges" title="Byte Ranges">Section 6.4.1</a>), a byte-range-resp-spec <em class="bcp14">MUST</em> only specify one range, and <em class="bcp14">MUST</em> contain absolute byte positions for both the first and last byte of the range.
+ </p>
+ <p id="rfc.section.6.2.p.5">A byte-content-range-spec with a byte-range-resp-spec whose last-byte-pos value is less than its first-byte-pos value, or
+ whose instance-length value is less than or equal to its last-byte-pos value, is invalid. The recipient of an invalid byte-content-range-spec <em class="bcp14">MUST</em> ignore it and any content transferred along with it.
+ </p>
+ <p id="rfc.section.6.2.p.6">A server sending a response with status code 416 (Requested range not satisfiable) <em class="bcp14">SHOULD</em> include a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the
+ selected resource. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".
+ </p>
+ <p id="rfc.section.6.2.p.7">Examples of byte-content-range-spec values, assuming that the entity contains a total of 1234 bytes: </p>
+ <ul>
+ <li>The first 500 bytes:
+ <div id="rfc.figure.u.6"></div><pre class="text"> bytes 0-499/1234
+</pre> </li>
+ <li>The second 500 bytes:
+ <div id="rfc.figure.u.7"></div><pre class="text"> bytes 500-999/1234
+</pre> </li>
+ <li>All except for the first 500 bytes:
+ <div id="rfc.figure.u.8"></div><pre class="text"> bytes 500-1233/1234
+</pre> </li>
+ <li>The last 500 bytes:
+ <div id="rfc.figure.u.9"></div><pre class="text"> bytes 734-1233/1234
+</pre> </li>
+ </ul>
+ <p id="rfc.section.6.2.p.8">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to
+ a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header, and
+ a Content-Length header showing the number of bytes actually transferred. For example,
+ </p>
+ <div id="rfc.figure.u.10"></div><pre class="text"> HTTP/1.1 206 Partial content
Date: Wed, 15 Nov 1995 06:25:24 GMT
Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
Content-Range: bytes 21010-47021/47022
Content-Length: 26012
Content-Type: image/gif
-</pre><p id="rfc.section.6.2.p.10">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges" as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>. See <a href="#changes.from.rfc.2068" title="Changes from RFC 2068">Appendix B</a> for a compatibility issue.</p><p id="rfc.section.6.2.p.11">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple byte-ranges in a s
ingle request.</p><p id="rfc.section.6.2.p.12">When a client requests multiple byte-ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.</p><p id="rfc.section.6.2.p.13">If the server ignores a byte-range-spec because it is syntactically invalid, the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing the full entity).</p><p id="rfc.section.6.2.p.14">If the server receives a request (other than one including an If-Range request-header field) with an unsatisfiable Range request-header field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected resource), it <em class="bcp14">SHOULD</em> return a response code of 416 (Requested range not satisfiable) (<a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Sat
isfiable">Section 4</a>). </p><dl class="empty"><dd> <b>Note:</b> clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for an unsatisfiable Range request-header, since not all servers implement this request-header.</dd></dl><div id="rfc.iref.i.1"></div><div id="rfc.iref.h.3"></div><h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a> <a id="header.if-range" href="#header.if-range">If-Range</a></h2><p id="rfc.section.6.3.p.1">If a client has a partial copy of an entity in its cache, and wishes to have an up-to-date copy of the entire entity in its cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and If-Match.) However, if the condition fails because the entity has been modified, the client would then have to make a second request to obtain the entire current entity-body.</p><p id="rfc.section.6.3.p.2">The If-Range header allows a
client to "short-circuit" the second request. Informally, its meaning is `if the entity is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity'.</p><div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.11"></span> If-Range = "If-Range" ":" ( entity-tag | HTTP-date )
-</pre><p id="rfc.section.6.3.p.4">If the client has no entity tag for an entity, but does have a Last-Modified date, it <em class="bcp14">MAY</em> use that date in an If-Range header. (The server can distinguish between a valid HTTP-date and any form of entity-tag by examining no more than two characters.) The If-Range header <em class="bcp14">SHOULD</em> only be used together with a Range header, and <em class="bcp14">MUST</em> be ignored if the request does not include a Range header, or if the server does not support the sub-range operation.</p><p id="rfc.section.6.3.p.5">If the entity tag given in the If-Range header matches the current entity tag for the entity, then the server <em class="bcp14">SHOULD</em> provide the specified sub-range of the entity using a 206 (Partial content) response. If the entity tag does not match, then the server <em class="bcp14">SHOULD</em> return the entire entity using a 200 (OK) response.</p><div id="rfc.iref.r.1"></div><div id="rfc.iref
.h.4"></div><h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a> <a id="header.range" href="#header.range">Range</a></h2><h3 id="rfc.section.6.4.1"><a href="#rfc.section.6.4.1">6.4.1</a> <a id="byte.ranges" href="#byte.ranges">Byte Ranges</a></h3><p id="rfc.section.6.4.1.p.1">Since all HTTP entities are represented in HTTP messages as sequences of bytes, the concept of a byte range is meaningful for any HTTP entity. (However, not all clients and servers need to support byte-range operations.)</p><p id="rfc.section.6.4.1.p.2">Byte range specifications in HTTP apply to the sequence of bytes in the entity-body (not necessarily the same as the message-body).</p><p id="rfc.section.6.4.1.p.3">A byte range operation <em class="bcp14">MAY</em> specify a single range of bytes, or a set of ranges within a single entity.</p><div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span
><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span> ranges-specifier = byte-ranges-specifier
+</pre><p id="rfc.section.6.2.p.10">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping
+ ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
+ as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>. See <a href="#changes.from.rfc.2068" title="Changes from RFC 2068">Appendix B</a> for a compatibility issue.
+ </p>
+ <p id="rfc.section.6.2.p.11">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple byte-ranges in a single request.
+ </p>
+ <p id="rfc.section.6.2.p.12">When a client requests multiple byte-ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
+ </p>
+ <p id="rfc.section.6.2.p.13">If the server ignores a byte-range-spec because it is syntactically invalid, the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing
+ the full entity).
+ </p>
+ <p id="rfc.section.6.2.p.14">If the server receives a request (other than one including an If-Range request-header field) with an unsatisfiable Range request-header
+ field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
+ resource), it <em class="bcp14">SHOULD</em> return a response code of 416 (Requested range not satisfiable) (<a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section 4</a>).
+ </p>
+ <dl class="empty">
+ <dd> <b>Note:</b> clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for
+ an unsatisfiable Range request-header, since not all servers implement this request-header.
+ </dd>
+ </dl>
+ <div id="rfc.iref.i.1"></div>
+ <div id="rfc.iref.h.3"></div>
+ <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a> <a id="header.if-range" href="#header.if-range">If-Range</a></h2>
+ <p id="rfc.section.6.3.p.1">If a client has a partial copy of an entity in its cache, and wishes to have an up-to-date copy of the entire entity in its
+ cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and If-Match.)
+ However, if the condition fails because the entity has been modified, the client would then have to make a second request
+ to obtain the entire current entity-body.
+ </p>
+ <p id="rfc.section.6.3.p.2">The If-Range header allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity is unchanged,
+ send me the part(s) that I am missing; otherwise, send me the entire new entity'.
+ </p>
+ <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.11"></span> If-Range = "If-Range" ":" ( entity-tag | HTTP-date )
+</pre><p id="rfc.section.6.3.p.4">If the client has no entity tag for an entity, but does have a Last-Modified date, it <em class="bcp14">MAY</em> use that date in an If-Range header. (The server can distinguish between a valid HTTP-date and any form of entity-tag by examining
+ no more than two characters.) The If-Range header <em class="bcp14">SHOULD</em> only be used together with a Range header, and <em class="bcp14">MUST</em> be ignored if the request does not include a Range header, or if the server does not support the sub-range operation.
+ </p>
+ <p id="rfc.section.6.3.p.5">If the entity tag given in the If-Range header matches the current entity tag for the entity, then the server <em class="bcp14">SHOULD</em> provide the specified sub-range of the entity using a 206 (Partial content) response. If the entity tag does not match, then
+ the server <em class="bcp14">SHOULD</em> return the entire entity using a 200 (OK) response.
+ </p>
+ <div id="rfc.iref.r.1"></div>
+ <div id="rfc.iref.h.4"></div>
+ <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a> <a id="header.range" href="#header.range">Range</a></h2>
+ <h3 id="rfc.section.6.4.1"><a href="#rfc.section.6.4.1">6.4.1</a> <a id="byte.ranges" href="#byte.ranges">Byte Ranges</a></h3>
+ <p id="rfc.section.6.4.1.p.1">Since all HTTP entities are represented in HTTP messages as sequences of bytes, the concept of a byte range is meaningful
+ for any HTTP entity. (However, not all clients and servers need to support byte-range operations.)
+ </p>
+ <p id="rfc.section.6.4.1.p.2">Byte range specifications in HTTP apply to the sequence of bytes in the entity-body (not necessarily the same as the message-body).</p>
+ <p id="rfc.section.6.4.1.p.3">A byte range operation <em class="bcp14">MAY</em> specify a single range of bytes, or a set of ranges within a single entity.
+ </p>
+ <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span> ranges-specifier = byte-ranges-specifier
byte-ranges-specifier = bytes-unit "=" byte-range-set
byte-range-set = 1#( byte-range-spec | suffix-byte-range-spec )
byte-range-spec = first-byte-pos "-" [last-byte-pos]
first-byte-pos = 1*DIGIT
last-byte-pos = 1*DIGIT
-</pre><p id="rfc.section.6.4.1.p.5">The first-byte-pos value in a byte-range-spec gives the byte-offset of the first byte in a range. The last-byte-pos value gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start at zero.</p><p id="rfc.section.6.4.1.p.6">If the last-byte-pos value is present, it <em class="bcp14">MUST</em> be greater than or equal to the first-byte-pos in that byte-range-spec, or the byte-range-spec is syntactically invalid. The recipient of a byte-range-set that includes one or more syntactically invalid byte-range-spec values <em class="bcp14">MUST</em> ignore the header field that includes that byte-range-set.</p><p id="rfc.section.6.4.1.p.7">If the last-byte-pos value is absent, or if the value is greater than or equal to the current length of the entity-body, last-byte-pos is taken to be equal to one less than the current length of the entity-body in bytes.</p><p id="rfc.section.6.4.1
.p.8">By its choice of last-byte-pos, a client can limit the number of bytes retrieved without knowing the size of the entity.</p><div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span> suffix-byte-range-spec = "-" suffix-length
+</pre><p id="rfc.section.6.4.1.p.5">The first-byte-pos value in a byte-range-spec gives the byte-offset of the first byte in a range. The last-byte-pos value
+ gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
+ at zero.
+ </p>
+ <p id="rfc.section.6.4.1.p.6">If the last-byte-pos value is present, it <em class="bcp14">MUST</em> be greater than or equal to the first-byte-pos in that byte-range-spec, or the byte-range-spec is syntactically invalid. The
+ recipient of a byte-range-set that includes one or more syntactically invalid byte-range-spec values <em class="bcp14">MUST</em> ignore the header field that includes that byte-range-set.
+ </p>
+ <p id="rfc.section.6.4.1.p.7">If the last-byte-pos value is absent, or if the value is greater than or equal to the current length of the entity-body, last-byte-pos
+ is taken to be equal to one less than the current length of the entity-body in bytes.
+ </p>
+ <p id="rfc.section.6.4.1.p.8">By its choice of last-byte-pos, a client can limit the number of bytes retrieved without knowing the size of the entity.</p>
+ <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span> suffix-byte-range-spec = "-" suffix-length
suffix-length = 1*DIGIT
-</pre><p id="rfc.section.6.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the entity-body, of a length given by the suffix-length value. (That is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the entire entity-body is used.</p><p id="rfc.section.6.4.1.p.11">If a syntactically valid byte-range-set includes at least one byte-range-spec whose first-byte-pos is less than the current length of the entity-body, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set is satisfiable. Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set is unsatisfiable, the server <em class="bcp14">SHOULD</em> return a response with a status of 416 (Requested range not satisfiable). Otherwise, the server <em class="bcp14">SHOULD</em> return a response with a status of 206 (Partial Content) containing the satisfiable ranges of the entity-body.</p><p id="rf
c.section.6.4.1.p.12">Examples of byte-ranges-specifier values (assuming an entity-body of length 10000): </p><ul><li>The first 500 bytes (byte offsets 0-499, inclusive): bytes=0-499</li><li>The second 500 bytes (byte offsets 500-999, inclusive): bytes=500-999</li><li>The final 500 bytes (byte offsets 9500-9999, inclusive): bytes=-500</li><li>Or bytes=9500-</li><li>The first and last bytes only (bytes 0 and 9999): bytes=0-0,-1</li><li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive): <br> bytes=500-600,601-999<br> bytes=500-700,601-999</li></ul><h3 id="rfc.section.6.4.2"><a href="#rfc.section.6.4.2">6.4.2</a> Range Retrieval Requests</h3><p id="rfc.section.6.4.2.p.1">HTTP retrieval requests using conditional or unconditional GET methods <em class="bcp14">MAY</em> request one or more sub-ranges of the entity, instead of the entire entity, using the Range request header, which applies to the entity returned as the re
sult of the request:</p><div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.20"></span> Range = "Range" ":" ranges-specifier
-</pre><p id="rfc.section.6.4.2.p.3">A server <em class="bcp14">MAY</em> ignore the Range header. However, HTTP/1.1 origin servers and intermediate caches ought to support byte ranges when possible, since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large entities.</p><p id="rfc.section.6.4.2.p.4">If the server supports the Range header and the specified range or ranges are appropriate for the entity: </p><ul><li>The presence of a Range header in an unconditional GET modifies what is returned if the GET is otherwise successful. In other words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).</li><li>The presence of a Range header in a conditional GET (a request using one or both of If-Modified-Since and If-None-Match, or one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition is true. It does not affect the 3
04 (Not Modified) response returned if the conditional is false.</li></ul><p id="rfc.section.6.4.2.p.5">In some cases, it might be more appropriate to use the If-Range header (see <a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section 6.3</a>) in addition to the Range header.</p><p id="rfc.section.6.4.2.p.6">If a proxy that supports ranges receives a Range request, forwards the request to an inbound server, and receives an entire entity in reply, it <em class="bcp14">SHOULD</em> only return the requested range to its client. It <em class="bcp14">SHOULD</em> store the entire received response in its cache if that is consistent with its cache allocation policies.</p><h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> Acknowledgments</h1><p id="rfc.section.7.p.1">Most of the specification of ranges is based on work originally done by Ari Luotonen and John Franks, with additional input from Steve Zilles.</p><p id="rfc.section.7.p.2">Base
d on an XML translation of RFC 2616 by Julian Reschke.</p><h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> Security Considerations</h1><p id="rfc.section.8.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general [Part 1].</p><h1 id="rfc.references"><a href="#rfc.section.9" id="rfc.section.9">9.</a> References</h1><table summary="References"> <tr><td class="reference"><b id="RFC2046">[1]</b></td><td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC 2046, November 1996.</td></tr> <tr><td class="reference"><b id="RFC2616">[2]</b></td><td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title
="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2616, June 1999.</td></tr> </table><h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1><address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span><span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Department of Information and Computer Science</span><span class="adr"><span class="street-address vcardline">University of California, Irvine</span><span class="vcardline"><span class="locality">Irvine</span>, <span class="region">CA</span> <span class="postal-code">92697-3425</span></span></span><span class="vcardline tel"><span class="
type">Fax</span>: <a href="fax:+1(949)824-1715"><span class="value">+1(949)824-1715</span></a></span><span class="vcardline">EMail: <a><span class="email">fielding@ics.uci.edu</span></a></span></address><address class="vcard"><span class="vcardline"><span class="fn">James Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">James</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Laboratory for Computer Science, NE43-356</span><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span> <span class="postal-code">02139</span></span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)258-8682"><span class="value">+1(617)258-8682</span></a></span><span class="vcardline">EMail: <a><span class="email">jg@w3
.org</span></a></span></address><address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Compaq Computer Corporation</span><span class="adr"><span class="street-address vcardline">Western Research Laboratory</span><span class="street-address vcardline">250 University Avenue</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span> <span class="postal-code">94305</span></span></span><span class="vcardline">EMail: <a><span class="email">mogul@wrl.dec.com</span></a></span></address><address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcard
line">MIT Laboratory for Computer Science, NE43-356</span><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span> <span class="postal-code">02139</span></span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)258-8682"><span class="value">+1(617)258-8682</span></a></span><span class="vcardline">EMail: <a><span class="email">frystyk@w3.org</span></a></span></address><address class="vcard"><span class="vcardline"><span class="fn">Larry Masinter</span><span class="n hidden"><span class="family-name">Masinter</span><span class="given-name">Larry</span></span></span><span class="org vcardline">Xerox Corporation</span><span class="adr"><span class="street-address vcardline">MIT Laboratory for Computer Science, NE43-356</span><span class="street-address vcardline">3333 Coyote Hill Road</span><span class="vcardline"><span class="locality
">Palo Alto</span>, <span class="region">CA</span> <span class="postal-code">94034</span></span></span><span class="vcardline">EMail: <a><span class="email">masinter@parc.xerox.com</span></a></span></address><address class="vcard"><span class="vcardline"><span class="fn">Paul J. Leach</span><span class="n hidden"><span class="family-name">Leach</span><span class="given-name">Paul J.</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span> <span class="postal-code">98052</span></span></span><span class="vcardline">EMail: <a><span class="email">paulle@microsoft.com</span></a></span></address><address class="vcard"><span class="vcardline"><span class="fn">Tim Berners-Lee</span><span class="n hidden"><span class="family-name">Berners-Lee</span><span class="given-name">Tim</span></
span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Laboratory for Computer Science, NE43-356</span><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span> <span class="postal-code">02139</span></span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)258-8682"><span class="value">+1(617)258-8682</span></a></span><span class="vcardline">EMail: <a><span class="email">timbl@w3.org</span></a></span></address><div id="rfc.iref.m.1"></div><div id="rfc.iref.m.2"></div><h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a> <a id="internet.media.type.multipart.byteranges" href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></h1><p id="rfc.section.A.p.1">When an HTTP 206 (Partial Content) response message includes
the content of multiple ranges (a response to a request for multiple non-overlapping ranges), these are transmitted as a multipart message-body. The media type for this purpose is called "multipart/byteranges".</p><p id="rfc.section.A.p.2">The multipart/byteranges media type includes two or more parts, each with its own Content-Type and Content-Range fields. The required boundary parameter specifies the boundary string used to separate each body-part.</p><p id="rfc.section.A.p.3"> </p><dl><dt>Media Type name:</dt><dd>multipart</dd><dt>Media subtype name:</dt><dd>byteranges</dd><dt>Required parameters:</dt><dd>boundary</dd><dt>Optional parameters:</dt><dd>none</dd><dt>Encoding considerations:</dt><dd>only "7bit", "8bit", or "binary" are permitted</dd><dt>Security considerations:</dt><dd>none</dd></dl><div id="rfc.figure.u.15"></div><p>For example:</p><pre class="text"> HTTP/1.1 206 Partial Content
+</pre><p id="rfc.section.6.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the entity-body, of a length given by the suffix-length value. (That
+ is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the
+ entire entity-body is used.
+ </p>
+ <p id="rfc.section.6.4.1.p.11">If a syntactically valid byte-range-set includes at least one byte-range-spec whose first-byte-pos is less than the current
+ length of the entity-body, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set is
+ satisfiable. Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set is unsatisfiable, the server <em class="bcp14">SHOULD</em> return a response with a status of 416 (Requested range not satisfiable). Otherwise, the server <em class="bcp14">SHOULD</em> return a response with a status of 206 (Partial Content) containing the satisfiable ranges of the entity-body.
+ </p>
+ <p id="rfc.section.6.4.1.p.12">Examples of byte-ranges-specifier values (assuming an entity-body of length 10000): </p>
+ <ul>
+ <li>The first 500 bytes (byte offsets 0-499, inclusive): bytes=0-499</li>
+ <li>The second 500 bytes (byte offsets 500-999, inclusive): bytes=500-999</li>
+ <li>The final 500 bytes (byte offsets 9500-9999, inclusive): bytes=-500</li>
+ <li>Or bytes=9500-</li>
+ <li>The first and last bytes only (bytes 0 and 9999): bytes=0-0,-1</li>
+ <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive): <br> bytes=500-600,601-999<br> bytes=500-700,601-999
+ </li>
+ </ul>
+ <h3 id="rfc.section.6.4.2"><a href="#rfc.section.6.4.2">6.4.2</a> Range Retrieval Requests
+ </h3>
+ <p id="rfc.section.6.4.2.p.1">HTTP retrieval requests using conditional or unconditional GET methods <em class="bcp14">MAY</em> request one or more sub-ranges of the entity, instead of the entire entity, using the Range request header, which applies
+ to the entity returned as the result of the request:
+ </p>
+ <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.20"></span> Range = "Range" ":" ranges-specifier
+</pre><p id="rfc.section.6.4.2.p.3">A server <em class="bcp14">MAY</em> ignore the Range header. However, HTTP/1.1 origin servers and intermediate caches ought to support byte ranges when possible,
+ since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
+ entities.
+ </p>
+ <p id="rfc.section.6.4.2.p.4">If the server supports the Range header and the specified range or ranges are appropriate for the entity: </p>
+ <ul>
+ <li>The presence of a Range header in an unconditional GET modifies what is returned if the GET is otherwise successful. In other
+ words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).
+ </li>
+ <li>The presence of a Range header in a conditional GET (a request using one or both of If-Modified-Since and If-None-Match, or
+ one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
+ is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
+ </li>
+ </ul>
+ <p id="rfc.section.6.4.2.p.5">In some cases, it might be more appropriate to use the If-Range header (see <a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section 6.3</a>) in addition to the Range header.
+ </p>
+ <p id="rfc.section.6.4.2.p.6">If a proxy that supports ranges receives a Range request, forwards the request to an inbound server, and receives an entire
+ entity in reply, it <em class="bcp14">SHOULD</em> only return the requested range to its client. It <em class="bcp14">SHOULD</em> store the entire received response in its cache if that is consistent with its cache allocation policies.
+ </p>
+ <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> Acknowledgments
+ </h1>
+ <p id="rfc.section.7.p.1">Most of the specification of ranges is based on work originally done by Ari Luotonen and John Franks, with additional input
+ from Steve Zilles.
+ </p>
+ <p id="rfc.section.7.p.2">Based on an XML translation of RFC 2616 by Julian Reschke.</p>
+ <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> Security Considerations
+ </h1>
+ <p id="rfc.section.8.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general [Part 1].</p>
+ <h1 id="rfc.references"><a href="#rfc.section.9" id="rfc.section.9">9.</a> References
+ </h1>
+ <table summary="References">
+ <tr>
+ <td class="reference"><b id="RFC2046">[1]</b></td>
+ <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N. Borenstein</a>, â<a href="http://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>â, RFC 2046, November 1996.
+ </td>
+ </tr>
+ <tr>
+ <td class="reference"><b id="RFC2616">[2]</b></td>
+ <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="W3C">T. Berners-Lee</a>, â<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>â, RFC 2616, June 1999.
+ </td>
+ </tr>
+ </table>
+ <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
+ <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span><span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Department of Information and Computer Science</span><span class="adr"><span class="street-address vcardline">University of California, Irvine</span><span class="vcardline"><span class="locality">Irvine</span>, <span class="region">CA</span> <span class="postal-code">92697-3425</span></span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(949)824-1715"><span class="value">+1(949)824-1715</span></a></span><span class="vcardline">EMail: <a><span class="email">fielding@ics.uci.edu</span></a></span></address>
+ <address class="vcard"><span class="vcardline"><span class="fn">James Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">James</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Laboratory for Computer Science, NE43-356</span><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span> <span class="postal-code">02139</span></span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)258-8682"><span class="value">+1(617)258-8682</span></a></span><span class="vcardline">EMail: <a><span class="email">jg@w3.org</span></a></span></address>
+ <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Compaq Computer Corporation</span><span class="adr"><span class="street-address vcardline">Western Research Laboratory</span><span class="street-address vcardline">250 University Avenue</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span> <span class="postal-code">94305</span></span></span><span class="vcardline">EMail: <a><span class="email">mogul@wrl.dec.com</span></a></span></address>
+ <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Laboratory for Computer Science, NE43-356</span><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span> <span class="postal-code">02139</span></span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)258-8682"><span class="value">+1(617)258-8682</span></a></span><span class="vcardline">EMail: <a><span class="email">frystyk@w3.org</span></a></span></address>
+ <address class="vcard"><span class="vcardline"><span class="fn">Larry Masinter</span><span class="n hidden"><span class="family-name">Masinter</span><span class="given-name">Larry</span></span></span><span class="org vcardline">Xerox Corporation</span><span class="adr"><span class="street-address vcardline">MIT Laboratory for Computer Science, NE43-356</span><span class="street-address vcardline">3333 Coyote Hill Road</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span> <span class="postal-code">94034</span></span></span><span class="vcardline">EMail: <a><span class="email">masinter@parc.xerox.com</span></a></span></address>
+ <address class="vcard"><span class="vcardline"><span class="fn">Paul J. Leach</span><span class="n hidden"><span class="family-name">Leach</span><span class="given-name">Paul J.</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span> <span class="postal-code">98052</span></span></span><span class="vcardline">EMail: <a><span class="email">paulle@microsoft.com</span></a></span></address>
+ <address class="vcard"><span class="vcardline"><span class="fn">Tim Berners-Lee</span><span class="n hidden"><span class="family-name">Berners-Lee</span><span class="given-name">Tim</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Laboratory for Computer Science, NE43-356</span><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span> <span class="postal-code">02139</span></span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)258-8682"><span class="value">+1(617)258-8682</span></a></span><span class="vcardline">EMail: <a><span class="email">timbl@w3.org</span></a></span></address>
+ <div id="rfc.iref.m.1"></div>
+ <div id="rfc.iref.m.2"></div>
+ <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a> <a id="internet.media.type.multipart.byteranges" href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></h1>
+ <p id="rfc.section.A.p.1">When an HTTP 206 (Partial Content) response message includes the content of multiple ranges (a response to a request for multiple
+ non-overlapping ranges), these are transmitted as a multipart message-body. The media type for this purpose is called "multipart/byteranges".
+ </p>
+ <p id="rfc.section.A.p.2">The multipart/byteranges media type includes two or more parts, each with its own Content-Type and Content-Range fields. The
+ required boundary parameter specifies the boundary string used to separate each body-part.
+ </p>
+ <p id="rfc.section.A.p.3"> </p>
+ <dl>
+ <dt>Media Type name:</dt>
+ <dd>multipart</dd>
+ <dt>Media subtype name:</dt>
+ <dd>byteranges</dd>
+ <dt>Required parameters:</dt>
+ <dd>boundary</dd>
+ <dt>Optional parameters:</dt>
+ <dd>none</dd>
+ <dt>Encoding considerations:</dt>
+ <dd>only "7bit", "8bit", or "binary" are permitted</dd>
+ <dt>Security considerations:</dt>
+ <dd>none</dd>
+ </dl>
+ <div id="rfc.figure.u.15"></div>
+ <p>For example:</p><pre class="text"> HTTP/1.1 206 Partial Content
Date: Wed, 15 Nov 1995 06:25:24 GMT
Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
@@ -381,4 +798,143 @@
...the second range
--THIS_STRING_SEPARATES--
[... 144 lines stripped ...]
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@labs.apache.org
For additional commands, e-mail: commits-help@labs.apache.org