Ignore:
Timestamp:
Jun 22, 2012, 12:32:37 AM (7 years ago)
Author:
julian.reschke@…
Message:

avoid the use of "may"/"should" when it could be confused with MAY/SHOULD

File:
1 edited

Legend:

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

    r1684 r1685  
    539539      <p>Part 5 defines range requests and the rules for constructing and combining responses to those requests.</p>
    540540      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    541       <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived
     541      <p>Discussion of this draft ought to take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived
    542542         at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
    543543      </p> 
     
    885885</pre> </li>
    886886      </ul>
    887       <p id="rfc.section.5.2.p.10">If the server ignores a byte-range-spec (for example if it is syntactically invalid, or if it may be seen as a denial-of-service
     887      <p id="rfc.section.5.2.p.10">If the server ignores a byte-range-spec (for example if it is syntactically invalid, or if it might be seen as a denial-of-service
    888888         attack), the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing
    889889         the full representation).
     
    11071107      </p>
    11081108      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="overlapping.ranges" href="#overlapping.ranges">Overlapping Ranges</a></h2>
    1109       <p id="rfc.section.7.1.p.1">Range requests containing overlapping ranges may lead to the situation where a server is sending far more data than the size
     1109      <p id="rfc.section.7.1.p.1">Range requests containing overlapping ranges can lead to the situation where a server is sending far more data than the size
    11101110         of the complete resource representation.
    11111111      </p>
Note: See TracChangeset for help on using the changeset viewer.