Ignore:
Timestamp:
Mar 3, 2010, 1:19:25 AM (10 years ago)
Author:
julian.reschke@…
Message:

Simplify discussion of history lists (see #197)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.html

    r764 r766  
    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-03-01">
     404      <meta name="dct.issued" scheme="ISO8601" content="2010-03-03">
    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: September 2, 2010</td>
     430               <td class="left">Expires: September 4, 2010</td>
    431431               <td class="right">J. Mogul</td>
    432432            </tr>
     
    489489            <tr>
    490490               <td class="left"></td>
    491                <td class="right">March 1, 2010</td>
     491               <td class="right">March 3, 2010</td>
    492492            </tr>
    493493         </tbody>
     
    519519      <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>.
    520520      </p>
    521       <p>This Internet-Draft will expire in September 2, 2010.</p>
     521      <p>This Internet-Draft will expire in September 4, 2010.</p>
    522522      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    523523      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    13771377         retrieved earlier in a session.
    13781378      </p>
    1379       <p id="rfc.section.4.p.2">History mechanisms and caches are different. In particular history mechanisms <em class="bcp14">SHOULD NOT</em> try to show a correct view of the current state of a resource. Rather, a history mechanism is meant to show exactly what the
    1380          user saw at the time when the resource was retrieved.
    1381       </p>
    1382       <p id="rfc.section.4.p.3">By default, an expiration time does not apply to history mechanisms. If the entity is still in storage, a history mechanism <em class="bcp14">SHOULD</em> display it even if the entity has expired, unless the user has specifically configured the agent to refresh expired history
    1383          documents.
    1384       </p>
    1385       <p id="rfc.section.4.p.4">This is not to be construed to prohibit the history mechanism from telling the user that a view might be stale.</p>
    1386       <div class="note" id="rfc.section.4.p.5">
    1387          <p> <b>Note:</b> If history list mechanisms unnecessarily prevent users from viewing stale resources, this will tend to force service authors
    1388             to avoid using HTTP expiration controls and cache controls when they would otherwise like to. Service authors may consider
    1389             it important that users not be presented with error messages or warning messages when they use navigation controls (such as
    1390             BACK) to view previously fetched resources. Even though sometimes such resources ought not be cached, or ought to expire quickly,
    1391             user interface considerations may force service authors to resort to other means of preventing caching (e.g., "once-only"
    1392             URLs) in order not to suffer the effects of improperly functioning history mechanisms.
    1393          </p>
    1394       </div>
     1379      <p id="rfc.section.4.p.2">The freshness model (<a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>) does not necessarily apply to history mechanisms. I.e., a history mechanism can display a previous representation even if
     1380         it has expired.
     1381      </p>
     1382      <p id="rfc.section.4.p.3">This does not prohibit the history mechanism from telling the user that a view might be stale, or from honoring cache directives
     1383         (e.g., Cache-Control: no-store).
     1384      </p>
    13951385      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    13961386      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="message.header.registration" href="#message.header.registration">Message Header Registration</a></h2>
     
    17541744      </ul>
    17551745      <h2 id="rfc.section.C.10"><a href="#rfc.section.C.10">C.10</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p6-cache-08</a></h2>
    1756       <p id="rfc.section.C.10.p.1">Affected issues: </p>
     1746      <p id="rfc.section.C.10.p.1">Closed issues: </p>
     1747      <ul>
     1748         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/197">http://tools.ietf.org/wg/httpbis/trac/ticket/197</a>&gt;: "Effect of CC directives on history lists"
     1749         </li>
     1750      </ul>
     1751      <p id="rfc.section.C.10.p.2">Affected issues: </p>
    17571752      <ul>
    17581753         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/199">http://tools.ietf.org/wg/httpbis/trac/ticket/199</a>&gt;: Status codes and caching
Note: See TracChangeset for help on using the changeset viewer.