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.xml

    r1684 r1685  
    115115<note title="Editorial Note (To be removed by RFC Editor)">
    116116  <t>
    117     Discussion of this draft should take place on the HTTPBIS working group
     117    Discussion of this draft ought to take place on the HTTPBIS working group
    118118    mailing list (ietf-http-wg@w3.org), which is archived at
    119119    <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
     
    623623<t>
    624624   If the server ignores a byte-range-spec (for example if it is
    625    syntactically invalid, or if it may be seen as a denial-of-service
     625   syntactically invalid, or if it might be seen as a denial-of-service
    626626   attack), the server &SHOULD; treat the request as if the invalid Range
    627627   header field did not exist. (Normally, this means return a 200
     
    963963<section title="Overlapping Ranges" anchor="overlapping.ranges">
    964964<t>
    965    Range requests containing overlapping ranges may lead to the situation
     965   Range requests containing overlapping ranges can lead to the situation
    966966   where a server is sending far more data than the size of the complete
    967967   resource representation.
Note: See TracChangeset for help on using the changeset viewer.