Changeset 2292 for draft-ietf-httpbis/latest
- Timestamp:
- 12/06/13 19:22:19 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r2290 r2292 449 449 } 450 450 @bottom-center { 451 content: "Expires December 1 3, 2013";451 content: "Expires December 14, 2013"; 452 452 } 453 453 @bottom-right { … … 492 492 <meta name="dct.creator" content="Reschke, J. F."> 493 493 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 494 <meta name="dct.issued" scheme="ISO8601" content="2013-06-1 1">494 <meta name="dct.issued" scheme="ISO8601" content="2013-06-12"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 496 496 <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."> … … 518 518 </tr> 519 519 <tr> 520 <td class="left">Expires: December 1 3, 2013</td>520 <td class="left">Expires: December 14, 2013</td> 521 521 <td class="right">J. Reschke, Editor</td> 522 522 </tr> … … 527 527 <tr> 528 528 <td class="left"></td> 529 <td class="right">June 1 1, 2013</td>529 <td class="right">June 12, 2013</td> 530 530 </tr> 531 531 </tbody> … … 552 552 in progress”. 553 553 </p> 554 <p>This Internet-Draft will expire on December 1 3, 2013.</p>554 <p>This Internet-Draft will expire on December 14, 2013.</p> 555 555 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 556 556 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 777 777 </p> 778 778 <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.17"></span> <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#imported.abnf" class="smpl">entity-tag</a> / <a href="#imported.abnf" class="smpl">HTTP-date</a> 779 </pre><p id="rfc.section.3.2.p.4"> Clients <em class="bcp14">MUST NOT</em> generate an entity-tag marked as weak in an If-Range field value and <em class="bcp14">MUST NOT</em> generate a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> date in an If-Range field value unless it has no entity-tag for the representation and the Last-Modified date it does have780 for the representation is strong in thesense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>.779 </pre><p id="rfc.section.3.2.p.4">A client <em class="bcp14">MUST NOT</em> generate an If-Range header field containing an entity-tag that is marked as weak. A client <em class="bcp14">MUST NOT</em> generate an If-Range header field containing a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> date unless the client has no entity-tag for the corresponding representation and the Last-Modified date is strong in the 780 sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>. 781 781 </p> 782 782 <p id="rfc.section.3.2.p.5">A server that evaluates a conditional range request that is applicable to one of its representations <em class="bcp14">MUST</em> evaluate the condition as false if the entity-tag used as a validator is marked as weak or, when an HTTP-date is used as the … … 835 835 support multipart responses. However, a server <em class="bcp14">MAY</em> generate a multipart/byteranges payload with only a single body part if multiple ranges were requested and only one range 836 836 was found to be satisfiable or only one range remained after coalescing. A client that cannot process a multipart/byteranges 837 response <em class="bcp14">MUST NOT</em> generate requests asking for multiple ranges in one single request.837 response <em class="bcp14">MUST NOT</em> generate a request that asks for multiple ranges. 838 838 </p> 839 839 <p id="rfc.section.4.1.p.9">When a multipart response payload is generated, the server <em class="bcp14">SHOULD</em> send the parts in the same order that the corresponding byte-range-spec appeared in the received <a href="#header.range" class="smpl">Range</a> header field, excluding those ranges that were deemed unsatisfiable or that were coalesced into other ranges. A client that -
draft-ietf-httpbis/latest/p5-range.xml
r2290 r2292 465 465 </artwork></figure> 466 466 <t> 467 Clients &MUST-NOT; generate an entity-tag marked as weak in an If-Range 468 field value and &MUST-NOT; generate a <x:ref>Last-Modified</x:ref> date in an 469 If-Range field value unless it has no entity-tag for the representation and 470 the Last-Modified date it does have for the representation is strong 467 A client &MUST-NOT; generate an If-Range header field containing an 468 entity-tag that is marked as weak. 469 A client &MUST-NOT; generate an If-Range header field containing a 470 <x:ref>Last-Modified</x:ref> date unless the client has no entity-tag for 471 the corresponding representation and the Last-Modified date is strong 471 472 in the sense defined by &lastmod-comparison;. 472 473 </t> … … 585 586 only one range remained after coalescing. 586 587 A client that cannot process a multipart/byteranges response &MUST-NOT; 587 generate requests asking for multiple ranges in one single request.588 generate a request that asks for multiple ranges. 588 589 </t> 589 590 <t>
Note: See TracChangeset
for help on using the changeset viewer.