Ignore:
Timestamp:
21/05/14 12:13:36 (6 years ago)
Author:
julian.reschke@…
Message:

editorial fixes (#553)

File:
1 edited

Legend:

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

    r2687 r2688  
    463463  }
    464464  @bottom-center {
    465        content: "Expires November 21, 2014";
     465       content: "Expires November 22, 2014";
    466466  }
    467467  @bottom-right {
     
    506506      <meta name="dct.creator" content="Reschke, J. F.">
    507507      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    508       <meta name="dct.issued" scheme="ISO8601" content="2014-05-20">
     508      <meta name="dct.issued" scheme="ISO8601" content="2014-05-21">
    509509      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    510510      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless 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.">
     
    532532            </tr>
    533533            <tr>
    534                <td class="left">Expires: November 21, 2014</td>
     534               <td class="left">Expires: November 22, 2014</td>
    535535               <td class="right">J. Reschke, Editor</td>
    536536            </tr>
     
    541541            <tr>
    542542               <td class="left"></td>
    543                <td class="right">May 20, 2014</td>
     543               <td class="right">May 21, 2014</td>
    544544            </tr>
    545545         </tbody>
     
    568568            in progress”.
    569569         </p>
    570          <p>This Internet-Draft will expire on November 21, 2014.</p>
     570         <p>This Internet-Draft will expire on November 22, 2014.</p>
    571571      </div>
    572572      <div id="rfc.copyrightnotice">
     
    627627         </li>
    628628         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
    629                <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#overlapping.ranges">Denial of Service Attacks using Range</a></li>
     629               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#overlapping.ranges">Denial-of-Service Attacks Using Range</a></li>
    630630            </ul>
    631631         </li>
     
    778778            </p>
    779779            <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
    780                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
     780               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
    781781               same data.
    782782            </p>
     
    922922            <div id="rfc.figure.u.22"></div><pre class="text">  Content-Range: bytes */1234
    923923</pre><p id="rfc.section.4.2.p.12">The complete-length in a 416 response indicates the current length of the selected representation.</p>
    924             <p id="rfc.section.4.2.p.13">The "Content-Range" header field has no meaning for status codes that do not explicitly describe its semantic. For this specification,
     924            <p id="rfc.section.4.2.p.13">The Content-Range header field has no meaning for status codes that do not explicitly describe its semantic. For this specification,
    925925               only the <a href="#status.206" class="smpl">206 (Partial Content)</a> and <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> status codes describe a meaning for Content-Range.
    926926            </p>
     
    985985            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#range.unit.registry">Range Unit Registry</a></h2>
    986986            <p id="rfc.section.5.1.p.1">The "HTTP Range Unit Registry" defines the namespace for the range unit names and refers to their corresponding specifications.
    987                The registry will be created and maintained at (the suggested URI) &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
     987               The registry has been created and is now maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
    988988            </p>
    989989            <div id="range.unit.registry.procedure">
     
    11801180         </p>
    11811181         <div id="overlapping.ranges">
    1182             <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            <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>
    11831183            <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
    11841184               many overlapping ranges of the same data is tiny compared to the time, memory, and bandwidth consumed by attempting to serve
Note: See TracChangeset for help on using the changeset viewer.