Ignore:
Timestamp:
01/07/13 08:47:55 (7 years ago)
Author:
julian.reschke@…
Message:

bump up document dates; update to latest version of rfc2629.xslt

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.html

    r2299 r2301  
    440440  }
    441441  @top-right {
    442        content: "June 2013";
     442       content: "July 2013";
    443443  }
    444444  @top-center {
     
    449449  }
    450450  @bottom-center {
    451        content: "Expires December 22, 2013";
     451       content: "Expires January 2, 2014";
    452452  }
    453453  @bottom-right {
     
    486486      <link href="p4-conditional.html" rel="prev">
    487487      <link href="p6-cache.html" rel="next">
    488       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.597, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     488      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    489489      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    490490      <meta name="dct.creator" content="Fielding, R.">
     
    492492      <meta name="dct.creator" content="Reschke, J. F.">
    493493      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    494       <meta name="dct.issued" scheme="ISO8601" content="2013-06-20">
     494      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    496496      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
     
    518518            </tr>
    519519            <tr>
    520                <td class="left">Expires: December 22, 2013</td>
     520               <td class="left">Expires: January 2, 2014</td>
    521521               <td class="right">J. Reschke, Editor</td>
    522522            </tr>
     
    527527            <tr>
    528528               <td class="left"></td>
    529                <td class="right">June 20, 2013</td>
     529               <td class="right">July 1, 2013</td>
    530530            </tr>
    531531         </tbody>
     
    552552         in progress”.
    553553      </p>
    554       <p>This Internet-Draft will expire on December 22, 2013.</p>
     554      <p>This Internet-Draft will expire on January 2, 2014.</p>
    555555      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    556556      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    662662      <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span>  <a href="#byte.ranges" class="smpl">bytes-unit</a>       = "bytes"
    663663</pre><div id="rule.ranges-specifier">
    664          <p id="rfc.section.2.1.p.3">                A byte range request can specify a single range of bytes, or a set of ranges within a single representation.</p>
     664         <p id="rfc.section.2.1.p.3">        A byte range request can specify a single range of bytes, or a set of ranges within a single representation.</p>
    665665      </div>
    666666      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.5"></span><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>  <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#byte.ranges" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>
     
    878878</pre><p id="rfc.section.4.2.p.7">and this second example illustrates when the complete length is unknown:</p>
    879879      <div id="rfc.figure.u.21"></div><pre class="text">  Content-Range: bytes 42-1233/*
    880 </pre><p id="rfc.section.4.2.p.9">A Content-Range field value is invalid if it contains a <a href="#header.content-range" class="smpl">byte-range-resp</a> that has a <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value less than its <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> value, or a <a href="#header.content-range" class="smpl">complete-length</a> value less than or equal to its <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value. The recipient of an invalid <a href="#header.content-range" class="smpl">Content-Range</a>  <em class="bcp14">MUST NOT</em> attempt to recombine the received content with a stored representation.
     880</pre><p id="rfc.section.4.2.p.9">A Content-Range field value is invalid if it contains a <a href="#header.content-range" class="smpl">byte-range-resp</a> that has a <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value less than its <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> value, or a <a href="#header.content-range" class="smpl">complete-length</a> value less than or equal to its <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value. The recipient of an invalid <a href="#header.content-range" class="smpl">Content-Range</a> <em class="bcp14">MUST NOT</em> attempt to recombine the received content with a stored representation.
    881881      </p>
    882882      <p id="rfc.section.4.2.p.10">A server generating a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response to a byte range request <em class="bcp14">SHOULD</em> send a Content-Range header field with an <a href="#header.content-range" class="smpl">unsatisfied-range</a> value, as in the following example:
     
    932932Date: Fri, 20 Jan 2012 15:41:54 GMT
    933933Content-Range: bytes */47022
    934 </pre><div class="note" id="rfc.section.4.4.p.4"> 
    935          <p> <b>Note:</b> Because servers are free to ignore <a href="#header.range" class="smpl">Range</a>, many implementations will simply respond with the entire selected representation in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. That is partly because most clients are prepared to receive a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> to complete the task (albeit less efficiently) and partly because clients might not stop making an invalid partial request
     934</pre><div class="note" id="rfc.section.4.4.p.4">
     935         <p><b>Note:</b> Because servers are free to ignore <a href="#header.range" class="smpl">Range</a>, many implementations will simply respond with the entire selected representation in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. That is partly because most clients are prepared to receive a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> to complete the task (albeit less efficiently) and partly because clients might not stop making an invalid partial request
    936936            until they have received a complete representation. Thus, clients cannot depend on receiving a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response even when it is most appropriate.
    937937         </p>
     
    996996                  <td class="left">206</td>
    997997                  <td class="left">Partial Content</td>
    998                   <td class="left"> <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;4.1</a>
     998                  <td class="left"><a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;4.1</a>
    999999                  </td>
    10001000               </tr>
     
    10021002                  <td class="left">416</td>
    10031003                  <td class="left">Range Not Satisfiable</td>
    1004                   <td class="left"> <a href="#status.416" id="rfc.xref.status.416.1" title="416 Range Not Satisfiable">Section&nbsp;4.4</a>
     1004                  <td class="left"><a href="#status.416" id="rfc.xref.status.416.1" title="416 Range Not Satisfiable">Section&nbsp;4.4</a>
    10051005                  </td>
    10061006               </tr>
     
    10301030                  <td class="left">http</td>
    10311031                  <td class="left">standard</td>
    1032                   <td class="left"> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.3" title="Accept-Ranges">Section&nbsp;2.3</a>
     1032                  <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.3" title="Accept-Ranges">Section&nbsp;2.3</a>
    10331033                  </td>
    10341034               </tr>
     
    10371037                  <td class="left">http</td>
    10381038                  <td class="left">standard</td>
    1039                   <td class="left"> <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;4.2</a>
     1039                  <td class="left"><a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;4.2</a>
    10401040                  </td>
    10411041               </tr>
     
    10441044                  <td class="left">http</td>
    10451045                  <td class="left">standard</td>
    1046                   <td class="left"> <a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;3.2</a>
     1046                  <td class="left"><a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;3.2</a>
    10471047                  </td>
    10481048               </tr>
     
    10511051                  <td class="left">http</td>
    10521052                  <td class="left">standard</td>
    1053                   <td class="left"> <a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;3.1</a>
     1053                  <td class="left"><a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;3.1</a>
    10541054                  </td>
    10551055               </tr>
     
    10791079         <tr>
    10801080            <td class="reference"><b id="Part1">[Part1]</b></td>
    1081             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), June&nbsp;2013.
     1081            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), July&nbsp;2013.
    10821082            </td>
    10831083         </tr>
    10841084         <tr>
    10851085            <td class="reference"><b id="Part2">[Part2]</b></td>
    1086             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), June&nbsp;2013.
     1086            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), July&nbsp;2013.
    10871087            </td>
    10881088         </tr>
    10891089         <tr>
    10901090            <td class="reference"><b id="Part4">[Part4]</b></td>
    1091             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), June&nbsp;2013.
     1091            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), July&nbsp;2013.
    10921092            </td>
    10931093         </tr>
    10941094         <tr>
    10951095            <td class="reference"><b id="Part6">[Part6]</b></td>
    1096             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), June&nbsp;2013.
     1096            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), July&nbsp;2013.
    10971097            </td>
    10981098         </tr>
     
    11561156      <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more body 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.
    11571157      </p>
    1158       <p id="rfc.section.A.p.3"> </p>
     1158      <p id="rfc.section.A.p.3"></p>
    11591159      <dl>
    11601160         <dt>Type name:</dt>
     
    11781178         <dd>HTTP components supporting multiple ranges in a single request.</dd>
    11791179         <dt>Additional information:</dt>
    1180          <dd> 
     1180         <dd>
    11811181            <dl>
    11821182               <dt>Magic number(s):</dt>
     
    13101310      <p id="rfc.section.E.1.p.1">Closed issues: </p>
    13111311      <ul>
    1312          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/358">http://tools.ietf.org/wg/httpbis/trac/ticket/358</a>&gt;: "ABNF list expansion code problem"
    1313          </li>
    1314          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
    1315          </li>
    1316          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/367">http://tools.ietf.org/wg/httpbis/trac/ticket/367</a>&gt;: "reserve 'none' as byte range unit"
    1317          </li>
    1318          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>&gt;: "note introduction of new IANA registries as normative changes"
    1319          </li>
    1320          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/369">http://tools.ietf.org/wg/httpbis/trac/ticket/369</a>&gt;: "range units vs leading zeroes vs size"
     1312         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/358">http://tools.ietf.org/wg/httpbis/trac/ticket/358</a>&gt;: "ABNF list expansion code problem"
     1313         </li>
     1314         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
     1315         </li>
     1316         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/367">http://tools.ietf.org/wg/httpbis/trac/ticket/367</a>&gt;: "reserve 'none' as byte range unit"
     1317         </li>
     1318         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>&gt;: "note introduction of new IANA registries as normative changes"
     1319         </li>
     1320         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/369">http://tools.ietf.org/wg/httpbis/trac/ticket/369</a>&gt;: "range units vs leading zeroes vs size"
    13211321         </li>
    13221322      </ul>
    13231323      <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;<a id="changes.since.20" href="#changes.since.20">Since draft-ietf-httpbis-p5-range-20</a></h2>
    1324       <p id="rfc.section.E.2.p.1"> </p>
     1324      <p id="rfc.section.E.2.p.1"></p>
    13251325      <ul>
    13261326         <li>Conformance criteria and considerations regarding error handling are now defined in Part 1.</li>
     
    13291329      <p id="rfc.section.E.3.p.1">Closed issues: </p>
    13301330      <ul>
    1331          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/175">http://tools.ietf.org/wg/httpbis/trac/ticket/175</a>&gt;: "Security consideration: range flooding"
    1332          </li>
    1333          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
    1334          </li>
    1335          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/311">http://tools.ietf.org/wg/httpbis/trac/ticket/311</a>&gt;: "Add limitations to Range to reduce its use as a denial-of-service tool"
    1336          </li>
    1337          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/407">http://tools.ietf.org/wg/httpbis/trac/ticket/407</a>&gt;: "416 and multipart/byteranges"
     1331         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/175">http://tools.ietf.org/wg/httpbis/trac/ticket/175</a>&gt;: "Security consideration: range flooding"
     1332         </li>
     1333         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
     1334         </li>
     1335         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/311">http://tools.ietf.org/wg/httpbis/trac/ticket/311</a>&gt;: "Add limitations to Range to reduce its use as a denial-of-service tool"
     1336         </li>
     1337         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/407">http://tools.ietf.org/wg/httpbis/trac/ticket/407</a>&gt;: "416 and multipart/byteranges"
    13381338         </li>
    13391339      </ul>
     
    13411341      <p id="rfc.section.E.4.p.1">Closed issues: </p>
    13421342      <ul>
    1343          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>&gt;: "explain list expansion in ABNF appendices"
    1344          </li>
    1345          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/437">http://tools.ietf.org/wg/httpbis/trac/ticket/437</a>&gt;: "incorrect example dates"
    1346          </li>
    1347          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/438">http://tools.ietf.org/wg/httpbis/trac/ticket/438</a>&gt;: "media type registration template issues"
    1348          </li>
    1349          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/462">http://tools.ietf.org/wg/httpbis/trac/ticket/462</a>&gt;: "Editorial suggestions"
    1350          </li>
    1351          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/485">http://tools.ietf.org/wg/httpbis/trac/ticket/485</a>&gt;: "MUSTs and other feedback"
     1343         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>&gt;: "explain list expansion in ABNF appendices"
     1344         </li>
     1345         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/437">http://tools.ietf.org/wg/httpbis/trac/ticket/437</a>&gt;: "incorrect example dates"
     1346         </li>
     1347         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/438">http://tools.ietf.org/wg/httpbis/trac/ticket/438</a>&gt;: "media type registration template issues"
     1348         </li>
     1349         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/462">http://tools.ietf.org/wg/httpbis/trac/ticket/462</a>&gt;: "Editorial suggestions"
     1350         </li>
     1351         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/485">http://tools.ietf.org/wg/httpbis/trac/ticket/485</a>&gt;: "MUSTs and other feedback"
    13521352         </li>
    13531353      </ul>
Note: See TracChangeset for help on using the changeset viewer.