Changeset 96 for draft-ietf-httpbis/latest/p5-range.html
- Timestamp:
- 22/12/07 19:14:28 (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r95 r96 484 484 <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1> 485 485 <ul class="toc"> 486 <li class="tocline0">1. <a href="#introduction">Introduction</a></li> 486 <li class="tocline0">1. <a href="#introduction">Introduction</a><ul class="toc"> 487 <li class="tocline1">1.1 <a href="#intro.requirements">Requirements</a></li> 488 </ul> 489 </li> 487 490 <li class="tocline0">2. <a href="#range.units">Range Units</a></li> 488 491 <li class="tocline0">3. <a href="#rfc.section.3">Status Code Definitions</a><ul class="toc"> … … 517 520 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.2">[RFC2616]</cite> without edit. 518 521 </p> 522 <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a> <a id="intro.requirements" href="#intro.requirements">Requirements</a></h2> 523 <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" 524 in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>. 525 </p> 526 <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant." 527 </p> 519 528 <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="range.units" href="#range.units">Range Units</a></h1> 520 529 <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 … … 768 777 <h1 id="rfc.references"><a href="#rfc.section.9" id="rfc.section.9">9.</a> References 769 778 </h1> 770 <table summary="References"> 779 <table summary="References"> 771 780 <tr> 772 781 <td class="reference"><b id="Part1">[Part1]</b></td> … … 782 791 <td class="reference"><b id="RFC2046">[RFC2046]</b></td> 783 792 <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. 793 </td> 794 </tr> 795 <tr> 796 <td class="reference"><b id="RFC2119">[RFC2119]</b></td> 797 <td class="top"><a title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997. 784 798 </td> 785 799 </tr> … … 979 993 <li class="indline1">Range header <a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.range.3">3.2</a>, <a class="iref" href="#rfc.iref.r.1"><b>5.4</b></a></li> 980 994 <li class="indline1"><em>RFC2046</em> <a class="iref" href="#RFC2046"><b>9</b></a>, <a class="iref" href="#rfc.xref.RFC2046.1">A</a></li> 995 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>9</b></a></li> 981 996 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">§</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#RFC2616"><b>9</b></a></li> 982 997 </ul>
Note: See TracChangeset
for help on using the changeset viewer.