Ignore:
Timestamp:
Nov 28, 2012, 7:32:34 PM (7 years ago)
Author:
mnot@…
Message:

Update Changes from RFC2616 from issues list.

File:
1 edited

Legend:

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

    r2015 r2021  
    12961296
    12971297<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
     1298
     1299<t>
     1300  A weak validator cannot be used in a <x:ref>206</x:ref> response.
     1301  (<xref target="status.206"/>)
     1302</t>
     1303<t>
     1304  The Content-Range header field only has meaning when the status code
     1305  explicitly defines its use.
     1306  (<xref target="header.content-range" />)
     1307</t>
     1308<t>
     1309  Servers are given more leeway in what they return to a range request,
     1310  in order to mitigate malicious (or just greedy) clients.
     1311</t>
     1312<t>
     1313  multipart/byteranges can consist of a single part.
     1314  (<xref target="internet.media.type.multipart.byteranges"/>)
     1315</t>
    12981316<t>
    12991317  This specification introduces a Range Specifier Registry.
    13001318  (<xref target="range.specifier.registry"/>)
    1301 </t>
    1302 <t>
    1303   A weak validator cannot be used in a <x:ref>206</x:ref> response.
    1304   (<xref target="status.206"/>)
    1305 </t>
    1306 <t>
    1307   multipart/byteranges can consist of a single part.
    1308   (<xref target="internet.media.type.multipart.byteranges"/>)
    13091319</t>
    13101320</section>
Note: See TracChangeset for help on using the changeset viewer.