Changeset 1543


Ignore:
Timestamp:
Feb 20, 2012, 10:08:57 AM (8 years ago)
Author:
julian.reschke@…
Message:

tune changes for [1542] (see #311)

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

Legend:

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

    r1542 r1543  
    826826      <p id="rfc.section.3.2.p.2">When this status code is returned for a byte-range request, the response <em class="bcp14">SHOULD</em> include a Content-Range header field specifying the current length of the representation (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;5.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type. For example,
    827827      </p>
    828       <div id="rfc.figure.u.4"></div><pre class="text">  HTTP/1.1 416 Requested Range Not Satisfiable
    829   Date: Mon, 20 Jan 2012 15:41:54 GMT
    830   Content-Range: bytes */47022
    831   Content-Type: image/gif
     828      <div id="rfc.figure.u.4"></div><pre class="text">HTTP/1.1 416 Requested Range Not Satisfiable
     829Date: Mon, 20 Jan 2012 15:41:54 GMT
     830Content-Range: bytes */47022
     831Content-Type: image/gif
    832832</pre><div class="note" id="rfc.section.3.2.p.4">
    833833         <p> <b>Note:</b> Clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for
     
    843843         and a Content-Length header field showing the number of bytes actually transferred. For example,
    844844      </p>
    845       <div id="rfc.figure.u.5"></div><pre class="text">  HTTP/1.1 206 Partial Content
    846   Date: Wed, 15 Nov 1995 06:25:24 GMT
    847   Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
    848   Content-Range: bytes 21010-47021/47022
    849   Content-Length: 26012
    850   Content-Type: image/gif
     845      <div id="rfc.figure.u.5"></div><pre class="text">HTTP/1.1 206 Partial Content
     846Date: Wed, 15 Nov 1995 06:25:24 GMT
     847Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
     848Content-Range: bytes 21010-47021/47022
     849Content-Length: 26012
     850Content-Type: image/gif
    851851</pre><p id="rfc.section.4.1.p.3">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping
    852852         ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
    853853         as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>.
    854854      </p>
    855       <p id="rfc.section.4.1.p.4">A server can combine requested ranges when those ranges are overlapping (See <a href="#security.considerations" title="Security Considerations">Section&nbsp;7</a>).
     855      <p id="rfc.section.4.1.p.4">A server <em class="bcp14">MAY</em> combine requested ranges when those ranges are overlapping (see <a href="#security.considerations" title="Security Considerations">Section&nbsp;7</a>).
    856856      </p>
    857857      <p id="rfc.section.4.1.p.5">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple ranges in a single request.
  • draft-ietf-httpbis/latest/p5-range.xml

    r1542 r1543  
    458458   This response &MUST-NOT; use the multipart/byteranges content-type. For example,
    459459</t>
    460 <figure><artwork type="example">
    461   HTTP/1.1 416 Requested Range Not Satisfiable
    462   Date: Mon, 20 Jan 2012 15:41:54 GMT
    463   Content-Range: bytes */47022
    464   Content-Type: image/gif
     460<figure><artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
     461HTTP/1.1 416 Requested Range Not Satisfiable
     462Date: Mon, 20 Jan 2012 15:41:54 GMT
     463Content-Range: bytes */47022
     464Content-Type: image/gif
    465465</artwork></figure>
    466466<x:note>
     
    484484   field showing the number of bytes actually transferred. For example,
    485485</t>
    486 <figure><artwork type="example">
    487   HTTP/1.1 206 Partial Content
    488   Date: Wed, 15 Nov 1995 06:25:24 GMT
    489   Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
    490   Content-Range: bytes 21010-47021/47022
    491   Content-Length: 26012
    492   Content-Type: image/gif
     486<figure><artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
     487HTTP/1.1 206 Partial Content
     488Date: Wed, 15 Nov 1995 06:25:24 GMT
     489Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
     490Content-Range: bytes 21010-47021/47022
     491Content-Length: 26012
     492Content-Type: image/gif
    493493</artwork></figure>
    494494<t>
     
    501501<t>
    502502   A server &MAY; combine requested ranges when those ranges are overlapping
    503    (See <xref target="security.considerations"/>).
     503   (see <xref target="security.considerations"/>).
    504504</t>
    505505<t>
Note: See TracChangeset for help on using the changeset viewer.