Nov 2, 2008, 8:32:36 AM (11 years ago)

Resolve #133: multipart/byteranges can consist of a single part (closes #133).

1 edited


  • draft-ietf-httpbis/latest/p5-range.html

    r331 r332  
    473473         <tr>
    474474            <td class="header left"></td>
    475             <td class="header right">November 1, 2008</td>
     475            <td class="header right">November 2, 2008</td>
    476476         </tr>
    477477      </table>
    971971         non-overlapping ranges), these are transmitted as a multipart message-body (<a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="http://tools.ietf.org/html/rfc2046#section-5.1">Section 5.1</a>). The media type for this purpose is called "multipart/byteranges". The following is to be registered with IANA <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>.
    972972      </p>
    973       <p id="rfc.section.A.p.2">The multipart/byteranges media type includes two or more parts, each with its own Content-Type and Content-Range fields. The
     973      <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more parts, each with its own Content-Type and Content-Range fields. The
    974974         required boundary parameter specifies the boundary string used to separate each body-part.
    975975      </p>
    10591059      <p id="rfc.section.B.2.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;4.1</a>)
    10601060      </p>
     1061      <p id="rfc.section.B.2.p.2">Clarify that 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>)
     1062      </p>
    10611063      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    10621064      <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC2616
    10951097      <h2 id="rfc.section.C.5"><a href="#rfc.section.C.5">C.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></h2>
    10961098      <h2 id="rfc.section.C.6"><a href="#rfc.section.C.6">C.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></h2>
     1099      <p id="rfc.section.C.6.p.1">Closed issues: </p>
     1100      <ul>
     1101         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/133">http://tools.ietf.org/wg/httpbis/trac/ticket/133</a>&gt;: "multipart/byteranges minimum number of parts"
     1102         </li>
     1103      </ul>
    10971104      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    10981105      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
Note: See TracChangeset for help on using the changeset viewer.