Ignore:
Timestamp:
May 21, 2014, 5:13:36 AM (6 years ago)
Author:
julian.reschke@…
Message:

editorial fixes (#553)

File:
1 edited

Legend:

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

    r2687 r2688  
    721721</t>
    722722<t>
    723    The "Content-Range" header field has no meaning for status codes that do
     723   The Content-Range header field has no meaning for status codes that do
    724724   not explicitly describe its semantic. For this specification, only the
    725725   <x:ref>206 (Partial Content)</x:ref> and
     
    857857   The "HTTP Range Unit Registry" defines the namespace for the range
    858858   unit names and refers to their corresponding specifications.
    859    The registry will be created and maintained at (the suggested URI)
     859   The registry has been created and is now maintained at
    860860   <eref target="http://www.iana.org/assignments/http-parameters"/>.
    861861</t>
     
    10601060</t>
    10611061
    1062 <section title="Denial of Service Attacks using Range" anchor="overlapping.ranges">
     1062<section title="Denial-of-Service Attacks Using Range" anchor="overlapping.ranges">
    10631063<t>
    10641064   Unconstrained multiple range requests are susceptible to denial-of-service
Note: See TracChangeset for help on using the changeset viewer.