Changeset 698 for draft-ietf-httpbis/latest/p5-range.html
- Timestamp:
- 26/09/09 10:09:09 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r697 r698 396 396 <meta name="DC.Creator" content="Reschke, J. F."> 397 397 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 398 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-09-2 5">398 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-09-26"> 399 399 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 400 400 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."> … … 428 428 </tr> 429 429 <tr> 430 <td class="header left">Expires: March 29, 2010</td>430 <td class="header left">Expires: March 30, 2010</td> 431 431 <td class="header right">HP</td> 432 432 </tr> … … 481 481 <tr> 482 482 <td class="header left"></td> 483 <td class="header right">September 2 5, 2009</td>483 <td class="header right">September 26, 2009</td> 484 484 </tr> 485 485 </table> … … 505 505 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 506 506 </p> 507 <p>This Internet-Draft will expire in March 29, 2010.</p>507 <p>This Internet-Draft will expire in March 30, 2010.</p> 508 508 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 509 509 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 694 694 <div id="rfc.iref.h.1"></div> 695 695 <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a> <a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2> 696 <p id="rfc.section.5.1.p.1">The "Accept-Ranges" response-header field allows the server to indicate its acceptance of range requests for a resource:</p>696 <p id="rfc.section.5.1.p.1">The "Accept-Ranges" response-header field allows a resource to indicate its acceptance of range requests.</p> 697 697 <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span> <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a> 698 698 <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a> = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> … … 864 864 </ul> 865 865 <h3 id="rfc.section.5.4.2"><a href="#rfc.section.5.4.2">5.4.2</a> <a id="range.retrieval.requests" href="#range.retrieval.requests">Range Retrieval Requests</a></h3> 866 <p id="rfc.section.5.4.2.p.1"> HTTP retrieval requests using conditional or unconditional GET methods <em class="bcp14">MAY</em> request one or more sub-ranges of the entity, instead of the entire entity, using the Range request header, which applies867 to the entity returned as the result of the request:866 <p id="rfc.section.5.4.2.p.1">The "Range" request-header field defines the GET method (conditional or not) to request one or more sub-ranges of the response 867 entity-body, instead of the entire entity body. 868 868 </p> 869 869 <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.23"></span> <a href="#range.retrieval.requests" class="smpl">Range</a> = "Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#range.retrieval.requests" class="smpl">Range-v</a>
Note: See TracChangeset
for help on using the changeset viewer.