Changeset 746 for draft-ietf-httpbis/latest/p5-range.html
- Timestamp:
- 17/01/10 14:33:08 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r741 r746 400 400 <meta name="DC.Creator" content="Reschke, J. F."> 401 401 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 402 <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01- 01">402 <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-17"> 403 403 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 404 404 <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."> … … 426 426 </tr> 427 427 <tr> 428 <td class="left">Expires: July 5, 2010</td>428 <td class="left">Expires: July 21, 2010</td> 429 429 <td class="right">J. Mogul</td> 430 430 </tr> … … 483 483 <tr> 484 484 <td class="left"></td> 485 <td class="right">January 1 , 2010</td>485 <td class="right">January 17, 2010</td> 486 486 </tr> 487 487 </tbody> … … 513 513 <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>>. 514 514 </p> 515 <p>This Internet-Draft will expire in July 5, 2010.</p>515 <p>This Internet-Draft will expire in July 21, 2010.</p> 516 516 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 517 517 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 800 800 to obtain the entire current entity-body. 801 801 </p> 802 <p id="rfc.section.5.3.p.2">The "If-Range" request-header field allows a client to "short-circuit" the second request. Informally, its meaning is `if803 the entity is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity '.802 <p id="rfc.section.5.3.p.2">The "If-Range" request-header field allows a client to "short-circuit" the second request. Informally, its meaning is "if 803 the entity is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity". 804 804 </p> 805 805 <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span> <a href="#header.if-range" class="smpl">If-Range</a> = "If-Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.if-range" class="smpl">If-Range-v</a>
Note: See TracChangeset
for help on using the changeset viewer.