Changeset 1044


Ignore:
Timestamp:
Oct 21, 2010, 7:54:34 PM (9 years ago)
Author:
mnot@…
Message:

Move warning about clockless caching to p6; fixes #204.

Location:
draft-ietf-httpbis/latest
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r1036 r1044  
    404404      <meta name="dct.creator" content="Reschke, J. F.">
    405405      <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">
    407407      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    408408      <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 &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations.">
     
    435435            </tr>
    436436            <tr>
    437                <td class="left">Expires: April 22, 2011</td>
     437               <td class="left">Expires: April 25, 2011</td>
    438438               <td class="right">HP</td>
    439439            </tr>
     
    488488            <tr>
    489489               <td class="left"></td>
    490                <td class="right">October 19, 2010</td>
     490               <td class="right">October 22, 2010</td>
    491491            </tr>
    492492         </tbody>
     
    516516         in progress”.
    517517      </p>
    518       <p>This Internet-Draft will expire on April 22, 2011.</p>
     518      <p>This Internet-Draft will expire on April 25, 2011.</p>
    519519      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    520520      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    20702070      </ol>
    20712071      <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.
    20732073      </p>
    20742074      <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
     
    27192719      <h2 id="rfc.references.2"><a href="#rfc.section.13.2" id="rfc.section.13.2">13.2</a> Informative References
    27202720      </h2>
    2721       <table>                                               
     2721      <table>                                             
    27222722         <tr>
    27232723            <td class="reference"><b id="BCP97">[BCP97]</b></td>
     
    27442744            <td class="reference"><b id="RFC1123">[RFC1123]</b></td>
    27452745            <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&nbsp;3, RFC&nbsp;1123, October&nbsp;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&nbsp;1305, March&nbsp;1992.
    27512746            </td>
    27522747         </tr>
     
    37303725                     </ul>
    37313726                  </li>
    3732                   <li class="indline1"><em>RFC1305</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1305.1">9.3</a>, <a class="iref" href="#RFC1305"><b>13.2</b></a></li>
    37333727                  <li class="indline1"><em>RFC1900</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1900.1">11.4</a>, <a class="iref" href="#RFC1900"><b>13.2</b></a></li>
    37343728                  <li class="indline1"><em>RFC1945</em>&nbsp;&nbsp;<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  
    30023002   A received message that does not have a Date header field &MUST; be
    30033003   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.
    30093005</t>
    30103006<t>
     
    42964292</reference>
    42974293
    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 
    43104294<reference anchor="RFC1900">
    43114295  <front>
  • draft-ietf-httpbis/latest/p6-cache.html

    r1026 r1044  
    402402      <meta name="dct.creator" content="Reschke, J. F.">
    403403      <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">
    405405      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    406406      <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 &#34;HTTP/1.1&#34; 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.">
     
    428428            </tr>
    429429            <tr>
    430                <td class="left">Expires: April 10, 2011</td>
     430               <td class="left">Expires: April 25, 2011</td>
    431431               <td class="right">J. Mogul</td>
    432432            </tr>
     
    489489            <tr>
    490490               <td class="left"></td>
    491                <td class="right">October 7, 2010</td>
     491               <td class="right">October 22, 2010</td>
    492492            </tr>
    493493         </tbody>
     
    515515         in progress”.
    516516      </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>
    518518      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    519519      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    790790         use.
    791791      </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>
    792794      <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="expiration.model" href="#expiration.model">Freshness Model</a></h2>
    793795      <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,
     
    871873      <ul class="empty">
    872874         <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.
    874876         </li>
    875877      </ul>
     
    20952097            </li>
    20962098            <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>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>
    20982100                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.3</a>, <a class="iref" href="#RFC2119"><b>8.1</b></a></li>
    20992101                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<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  
    547547   no-cache" to disambiguate which response to use.
    548548</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
    549556</section>
    550557
Note: See TracChangeset for help on using the changeset viewer.