Changeset 2363
- Timestamp:
- 28/08/13 14:03:43 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r2358 r2363 449 449 } 450 450 @bottom-center { 451 content: "Expires February 13, 2014";451 content: "Expires March 1, 2014"; 452 452 } 453 453 @bottom-right { … … 492 492 <meta name="dct.creator" content="Reschke, J. F."> 493 493 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 494 <meta name="dct.issued" scheme="ISO8601" content="2013-08- 12">494 <meta name="dct.issued" scheme="ISO8601" content="2013-08-28"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 496 496 <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."> … … 518 518 </tr> 519 519 <tr> 520 <td class="left">Expires: February 13, 2014</td>520 <td class="left">Expires: March 1, 2014</td> 521 521 <td class="right">J. Reschke, Editor</td> 522 522 </tr> … … 527 527 <tr> 528 528 <td class="left"></td> 529 <td class="right">August 12, 2013</td>529 <td class="right">August 28, 2013</td> 530 530 </tr> 531 531 </tbody> … … 552 552 in progress”. 553 553 </p> 554 <p>This Internet-Draft will expire on February 13, 2014.</p>554 <p>This Internet-Draft will expire on March 1, 2014.</p> 555 555 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 556 556 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 744 744 server <em class="bcp14">MUST</em> ignore a Range header field received with a request method other than GET. 745 745 </p> 746 <p id="rfc.section.3.1.p.4">An origin server <em class="bcp14">MUST</em> ignore a Range header field that contains a range unit it does not understand. A proxy <em class="bcp14">MAY</em> either discard a Range header field that contains a range unit it does not understand or pass it to the next inbound server 747 when forwarding the request. 748 </p> 749 <p id="rfc.section.3.1.p.5">A server that supports range requests ought to ignore or reject a <a href="#header.range" class="smpl">Range</a> header field that consists of more than two overlapping ranges, or a set of many small ranges that are not listed in ascending 746 <p id="rfc.section.3.1.p.4">An origin server <em class="bcp14">MUST</em> ignore a Range header field that contains a range unit it does not understand. A proxy <em class="bcp14">MAY</em> discard a Range header field that contains a range unit it does not understand. 747 </p> 748 <p id="rfc.section.3.1.p.5">A server that supports range requests <em class="bcp14">MAY</em> ignore or reject a <a href="#header.range" class="smpl">Range</a> header field that consists of more than two overlapping ranges, or a set of many small ranges that are not listed in ascending 750 749 order, since both are indications of either a broken client or a deliberate denial of service attack (<a href="#overlapping.ranges" title="Denial of Service Attacks using Range">Section 6.1</a>). A client <em class="bcp14">SHOULD NOT</em> request multiple ranges that are inherently less efficient to process and transfer than a single range that encompasses the 751 750 same data. … … 1354 1353 </ul> 1355 1354 <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a> <a id="changes.since.23" href="#changes.since.23">Since draft-ietf-httpbis-p5-range-23</a></h2> 1356 <p id="rfc.section.E.5.p.1">None yet.</p> 1355 <p id="rfc.section.E.5.p.1">Closed issues: </p> 1356 <ul> 1357 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/490">http://tools.ietf.org/wg/httpbis/trac/ticket/490</a>>: "p5 editorial comments" 1358 </li> 1359 </ul> 1357 1360 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1358 1361 <p class="noprint"><a href="#rfc.index.2">2</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> -
draft-ietf-httpbis/latest/p5-range.xml
r2358 r2363 392 392 <t> 393 393 An origin server &MUST; ignore a Range header field that contains a range 394 unit it does not understand. A proxy &MAY; either discard a Range header 395 field that contains a range unit it does not understand or pass it to the 396 next inbound server when forwarding the request. 397 </t> 398 <t> 399 A server that supports range requests ought to ignore or reject a 394 unit it does not understand. A proxy &MAY; discard a Range header 395 field that contains a range unit it does not understand. 396 </t> 397 <t> 398 A server that supports range requests &MAY; ignore or reject a 400 399 <x:ref>Range</x:ref> header field that consists of more than two 401 400 overlapping ranges, or a set of many small ranges that are not listed … … 1585 1584 <section title="Since draft-ietf-httpbis-p5-range-23" anchor="changes.since.23"> 1586 1585 <t> 1587 None yet. 1586 Closed issues: 1587 <list style="symbols"> 1588 <t> 1589 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/490"/>: 1590 "p5 editorial comments" 1591 </t> 1592 </list> 1588 1593 </t> 1589 1594 </section>
Note: See TracChangeset
for help on using the changeset viewer.