Changeset 2021


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

Update Changes from RFC2616 from issues list.

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r2018 r2021  
    12291229      </ol>
    12301230      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
    1231       <p id="rfc.section.B.p.1">This specification introduces a Range Specifier Registry. (<a href="#range.specifier.registry" title="Range Specifier Registry">Section&nbsp;2.1</a>)
    1232       </p>
    1233       <p id="rfc.section.B.p.2">A weak validator cannot be used in a <a href="#status.206" class="smpl">206</a> response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)
    1234       </p>
    1235       <p id="rfc.section.B.p.3">multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
     1231      <p id="rfc.section.B.p.1">A weak validator cannot be used in a <a href="#status.206" class="smpl">206</a> response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)
     1232      </p>
     1233      <p id="rfc.section.B.p.2">The Content-Range header field only has meaning when the status code explicitly defines its use. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section&nbsp;5.2</a>)
     1234      </p>
     1235      <p id="rfc.section.B.p.3">Servers are given more leeway in what they return to a range request, in order to mitigate malicious (or just greedy) clients.</p>
     1236      <p id="rfc.section.B.p.4">multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
     1237      </p>
     1238      <p id="rfc.section.B.p.5">This specification introduces a Range Specifier Registry. (<a href="#range.specifier.registry" title="Range Specifier Registry">Section&nbsp;2.1</a>)
    12361239      </p>
    12371240      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1>
     
    13371340            </li>
    13381341            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
    1339                   <li>Content-Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.xref.header.content-range.2">3.1</a>, <a href="#rfc.xref.header.content-range.3">3.2</a>, <a href="#rfc.iref.c.1"><b>5.2</b></a>, <a href="#rfc.xref.header.content-range.4">6.2</a></li>
     1342                  <li>Content-Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.xref.header.content-range.2">3.1</a>, <a href="#rfc.xref.header.content-range.3">3.2</a>, <a href="#rfc.iref.c.1"><b>5.2</b></a>, <a href="#rfc.xref.header.content-range.4">6.2</a>, <a href="#rfc.xref.header.content-range.5">B</a></li>
    13401343               </ul>
    13411344            </li>
  • 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.