![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 1044 for draft-ietf-httpbis/latest
- Timestamp:
- 22/10/10 02:54:34 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
-
p1-messaging.html (modified) (8 diffs)
-
p1-messaging.xml (modified) (2 diffs)
-
p6-cache.html (modified) (7 diffs)
-
p6-cache.xml (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1036 r1044 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2010-10- 19">406 <meta name="dct.issued" scheme="ISO8601" content="2010-10-22"> 407 407 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 408 408 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> … … 435 435 </tr> 436 436 <tr> 437 <td class="left">Expires: April 2 2, 2011</td>437 <td class="left">Expires: April 25, 2011</td> 438 438 <td class="right">HP</td> 439 439 </tr> … … 488 488 <tr> 489 489 <td class="left"></td> 490 <td class="right">October 19, 2010</td>490 <td class="right">October 22, 2010</td> 491 491 </tr> 492 492 </tbody> … … 516 516 in progress”. 517 517 </p> 518 <p>This Internet-Draft will expire on April 2 2, 2011.</p>518 <p>This Internet-Draft will expire on April 25, 2011.</p> 519 519 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 520 520 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2070 2070 </ol> 2071 2071 <p id="rfc.section.9.3.p.6">A received message that does not have a Date header field <em class="bcp14">MUST</em> be assigned one by the recipient if the message will be cached by that recipient or gatewayed via a protocol which requires 2072 a Date. An HTTP implementation without a clock <em class="bcp14">MUST NOT</em> cache responses without revalidating them on every use. An HTTP cache, especially a shared cache, <em class="bcp14">SHOULD</em> use a mechanism, such as NTP <a href="#RFC1305" id="rfc.xref.RFC1305.1"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>, to synchronize its clock with a reliable external standard.2072 a Date. 2073 2073 </p> 2074 2074 <p id="rfc.section.9.3.p.7">Clients <em class="bcp14">SHOULD</em> only send a Date header field in messages that include a payload, as is usually the case for PUT and POST requests, and even … … 2719 2719 <h2 id="rfc.references.2"><a href="#rfc.section.13.2" id="rfc.section.13.2">13.2</a> Informative References 2720 2720 </h2> 2721 <table> 2721 <table> 2722 2722 <tr> 2723 2723 <td class="reference"><b id="BCP97">[BCP97]</b></td> … … 2744 2744 <td class="reference"><b id="RFC1123">[RFC1123]</b></td> 2745 2745 <td class="top"><a href="mailto:Braden@ISI.EDU" title="University of Southern California (USC), Information Sciences Institute">Braden, R.</a>, “<a href="http://tools.ietf.org/html/rfc1123">Requirements for Internet Hosts - Application and Support</a>”, STD 3, RFC 1123, October 1989. 2746 </td>2747 </tr>2748 <tr>2749 <td class="reference"><b id="RFC1305">[RFC1305]</b></td>2750 <td class="top"><a href="mailto:mills@udel.edu" title="University of Delaware, Electrical Engineering Department">Mills, D.</a>, “<a href="http://tools.ietf.org/html/rfc1305">Network Time Protocol (Version 3) Specification, Implementation</a>”, RFC 1305, March 1992.2751 2746 </td> 2752 2747 </tr> … … 3730 3725 </ul> 3731 3726 </li> 3732 <li class="indline1"><em>RFC1305</em> <a class="iref" href="#rfc.xref.RFC1305.1">9.3</a>, <a class="iref" href="#RFC1305"><b>13.2</b></a></li>3733 3727 <li class="indline1"><em>RFC1900</em> <a class="iref" href="#rfc.xref.RFC1900.1">11.4</a>, <a class="iref" href="#RFC1900"><b>13.2</b></a></li> 3734 3728 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#RFC1945"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1031 r1044 3002 3002 A received message that does not have a Date header field &MUST; be 3003 3003 assigned one by the recipient if the message will be cached by that 3004 recipient or gatewayed via a protocol which requires a Date. An HTTP 3005 implementation without a clock &MUST-NOT; cache responses without 3006 revalidating them on every use. An HTTP cache, especially a shared 3007 cache, &SHOULD; use a mechanism, such as NTP <xref target="RFC1305"/>, to synchronize its 3008 clock with a reliable external standard. 3004 recipient or gatewayed via a protocol which requires a Date. 3009 3005 </t> 3010 3006 <t> … … 4296 4292 </reference> 4297 4293 4298 <reference anchor="RFC1305">4299 <front>4300 <title>Network Time Protocol (Version 3) Specification, Implementation</title>4301 <author initials="D." surname="Mills" fullname="David L. Mills">4302 <organization>University of Delaware, Electrical Engineering Department</organization>4303 <address><email>mills@udel.edu</email></address>4304 </author>4305 <date month="March" year="1992"/>4306 </front>4307 <seriesInfo name="RFC" value="1305"/>4308 </reference>4309 4310 4294 <reference anchor="RFC1900"> 4311 4295 <front> -
draft-ietf-httpbis/latest/p6-cache.html
r1026 r1044 402 402 <meta name="dct.creator" content="Reschke, J. F."> 403 403 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 404 <meta name="dct.issued" scheme="ISO8601" content="2010-10- 07">404 <meta name="dct.issued" scheme="ISO8601" content="2010-10-22"> 405 405 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 406 406 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 428 428 </tr> 429 429 <tr> 430 <td class="left">Expires: April 10, 2011</td>430 <td class="left">Expires: April 25, 2011</td> 431 431 <td class="right">J. Mogul</td> 432 432 </tr> … … 489 489 <tr> 490 490 <td class="left"></td> 491 <td class="right">October 7, 2010</td>491 <td class="right">October 22, 2010</td> 492 492 </tr> 493 493 </tbody> … … 515 515 in progress”. 516 516 </p> 517 <p>This Internet-Draft will expire on April 10, 2011.</p>517 <p>This Internet-Draft will expire on April 25, 2011.</p> 518 518 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 519 519 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 790 790 use. 791 791 </p> 792 <p id="rfc.section.2.2.p.6">An HTTP implementation without a clock <em class="bcp14">MUST NOT</em> used stored responses without revalidating them on every use. An HTTP cache, especially a shared cache, <em class="bcp14">SHOULD</em> use a mechanism, such as NTP <a href="#RFC1305" id="rfc.xref.RFC1305.1"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>, to synchronize its clock with a reliable external standard. 793 </p> 792 794 <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a> <a id="expiration.model" href="#expiration.model">Freshness Model</a></h2> 793 795 <p id="rfc.section.2.3.p.1">When a response is "fresh" in the cache, it can be used to satisfy subsequent requests without contacting the origin server, … … 871 873 <ul class="empty"> 872 874 <li>The term "now" means "the current value of the clock at the host performing the calculation". Hosts that use HTTP, but especially 873 hosts running origin servers and caches, <em class="bcp14">SHOULD</em> use NTP (<a href="#RFC1305" id="rfc.xref.RFC1305. 1"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>) or some similar protocol to synchronize their clocks to a globally accurate time standard.875 hosts running origin servers and caches, <em class="bcp14">SHOULD</em> use NTP (<a href="#RFC1305" id="rfc.xref.RFC1305.2"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>) or some similar protocol to synchronize their clocks to a globally accurate time standard. 874 876 </li> 875 877 </ul> … … 2095 2097 </li> 2096 2098 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind"> 2097 <li class="indline1"><em>RFC1305</em> <a class="iref" href="#rfc.xref.RFC1305.1">2. 3.2</a>, <a class="iref" href="#RFC1305"><b>8.2</b></a></li>2099 <li class="indline1"><em>RFC1305</em> <a class="iref" href="#rfc.xref.RFC1305.1">2.2</a>, <a class="iref" href="#rfc.xref.RFC1305.2">2.3.2</a>, <a class="iref" href="#RFC1305"><b>8.2</b></a></li> 2098 2100 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.3</a>, <a class="iref" href="#RFC2119"><b>8.1</b></a></li> 2099 2101 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">2.3.1.1</a>, <a class="iref" href="#RFC2616"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">C.1</a><ul class="ind"> -
draft-ietf-httpbis/latest/p6-cache.xml
r1019 r1044 547 547 no-cache" to disambiguate which response to use. 548 548 </t> 549 <t> 550 An HTTP implementation without a clock &MUST-NOT; used stored responses 551 without revalidating them on every use. An HTTP cache, especially a shared 552 cache, &SHOULD; use a mechanism, such as NTP <xref target="RFC1305"/>, to 553 synchronize its clock with a reliable external standard. 554 </t> 555 549 556 </section> 550 557
Note: See TracChangeset
for help on using the changeset viewer.
