Ignore:
Timestamp:
04/09/13 11:49:18 (7 years ago)
Author:
julian.reschke@…
Message:

(editorial) reorganize/tune changes sections (see #493)

File:
1 edited

Legend:

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

    r2365 r2369  
    13581358
    13591359<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
    1360 
     1360<t>
     1361  Servers are given more leeway in how they respond to a range request,
     1362  in order to mitigate abuse by malicious (or just greedy) clients.
     1363  (<xref target="header.range"/>)
     1364</t>
    13611365<t>
    13621366  A weak validator cannot be used in a <x:ref>206</x:ref> response.
     
    13691373</t>
    13701374<t>
    1371   Servers are given more leeway in how they respond to a range request,
    1372   in order to mitigate abuse by malicious (or just greedy) clients.
     1375  This specification introduces a Range Unit Registry.
     1376  (<xref target="range.unit.registry"/>)
    13731377</t>
    13741378<t>
    13751379  multipart/byteranges can consist of a single part.
    13761380  (<xref target="internet.media.type.multipart.byteranges"/>)
    1377 </t>
    1378 <t>
    1379   This specification introduces a Range Unit Registry.
    1380   (<xref target="range.unit.registry"/>)
    13811381</t>
    13821382</section>
Note: See TracChangeset for help on using the changeset viewer.