Ignore:
Timestamp:
15/09/13 01:06:52 (7 years ago)
Author:
fielding@…
Message:

uniform terminology for header section instead of header block; this and [2400] addresses #234

File:
1 edited

Legend:

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

    r2378 r2401  
    446446  }
    447447  @bottom-center {
    448        content: "Expires March 17, 2014";
     448       content: "Expires March 18, 2014";
    449449  }
    450450  @bottom-right {
     
    489489      <meta name="dct.creator" content="Reschke, J. F.">
    490490      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    491       <meta name="dct.issued" scheme="ISO8601" content="2013-09-13">
     491      <meta name="dct.issued" scheme="ISO8601" content="2013-09-14">
    492492      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    493493      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
     
    515515            </tr>
    516516            <tr>
    517                <td class="left">Expires: March 17, 2014</td>
     517               <td class="left">Expires: March 18, 2014</td>
    518518               <td class="right">J. Reschke, Editor</td>
    519519            </tr>
     
    524524            <tr>
    525525               <td class="left"></td>
    526                <td class="right">September 13, 2013</td>
     526               <td class="right">September 14, 2013</td>
    527527            </tr>
    528528         </tbody>
     
    549549         in progress”.
    550550      </p>
    551       <p>This Internet-Draft will expire on March 17, 2014.</p>
     551      <p>This Internet-Draft will expire on March 18, 2014.</p>
    552552      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    553553      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    801801... 26012 bytes of partial image data ...
    802802</pre><p id="rfc.section.4.1.p.4">If multiple parts are being transferred, the server generating the 206 response <em class="bcp14">MUST</em> generate a "multipart/byteranges" payload, as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>, and a <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> header field containing the multipart/byteranges media type and its required boundary parameter. To avoid confusion with single
    803          part responses, a server <em class="bcp14">MUST NOT</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field in the HTTP header block of a multiple part response (this field will be sent in each part instead).
     803         part responses, a server <em class="bcp14">MUST NOT</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field in the HTTP header section of a multiple part response (this field will be sent in each part instead).
    804804      </p>
    805805      <p id="rfc.section.4.1.p.5">Within the header area of each body part in the multipart payload, the server <em class="bcp14">MUST</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field corresponding to the range being enclosed in that body part. If the selected representation would have had a <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> header field in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, the server <em class="bcp14">SHOULD</em> generate that same <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> field in the header area of each body part. For example:
Note: See TracChangeset for help on using the changeset viewer.