Changeset 1015 for draft-ietf-httpbis/latest
- Timestamp:
- 20/09/10 10:13:02 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r1002 r1015 400 400 <meta name="dct.creator" content="Reschke, J. F."> 401 401 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 402 <meta name="dct.issued" scheme="ISO8601" content="2010-09- 14">402 <meta name="dct.issued" scheme="ISO8601" content="2010-09-20"> 403 403 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 404 404 <meta name="dct.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: March 18, 2011</td>428 <td class="left">Expires: March 24, 2011</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">September 14, 2010</td>485 <td class="right">September 20, 2010</td> 486 486 </tr> 487 487 </tbody> … … 509 509 in progress”. 510 510 </p> 511 <p>This Internet-Draft will expire on March 18, 2011.</p>511 <p>This Internet-Draft will expire on March 24, 2011.</p> 512 512 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 513 513 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 915 915 </p> 916 916 <p id="rfc.section.5.4.2.p.6">If a proxy that supports ranges receives a Range request, forwards the request to an inbound server, and receives an entire 917 representation in reply, it <em class="bcp14"> SHOULD</em> only return the requested range to its client. It <em class="bcp14">SHOULD</em> store the entire received response in its cache if that is consistent with its cache allocation policies.917 representation in reply, it <em class="bcp14">MAY</em> only return the requested range to its client. 918 918 </p> 919 919 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> … … 1361 1361 </ul> 1362 1362 <h2 id="rfc.section.D.13"><a href="#rfc.section.D.13">D.13</a> <a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p5-range-11</a></h2> 1363 <p id="rfc.section.D.13.p.1">None yet.</p> 1363 <p id="rfc.section.D.13.p.1">Closed issues: </p> 1364 <ul> 1365 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/217">http://tools.ietf.org/wg/httpbis/trac/ticket/217</a>>: "Caches can't be required to serve ranges" 1366 </li> 1367 </ul> 1364 1368 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1365 1369 <p class="noprint"><a href="#rfc.index.2">2</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a>
Note: See TracChangeset
for help on using the changeset viewer.