Ignore:
Timestamp:
06/05/14 13:54:35 (6 years ago)
Author:
julian.reschke@…
Message:

whitespace/hyphenation (#553)

File:
1 edited

Legend:

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

    r2638 r2643  
    777777            </p>
    778778            <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
    779                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&nbsp;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
     779               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&nbsp;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
    780780               same data.
    781781            </p>
     
    11801180         <div id="overlapping.ranges">
    11811181            <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#overlapping.ranges">Denial of Service Attacks using Range</a></h2>
    1182             <p id="rfc.section.6.1.p.1">Unconstrained multiple range requests are susceptible to denial of service attacks because the effort required to request
     1182            <p id="rfc.section.6.1.p.1">Unconstrained multiple range requests are susceptible to denial-of-service attacks because the effort required to request
    11831183               many overlapping ranges of the same data is tiny compared to the time, memory, and bandwidth consumed by attempting to serve
    11841184               the requested data in many parts. Servers ought to ignore, coalesce, or reject egregious range requests, such as requests
Note: See TracChangeset for help on using the changeset viewer.