Ignore:
Timestamp:
15/07/12 17:51:16 (9 years ago)
Author:
julian.reschke@…
Message:

make links to cache directive definitions more specific

File:
1 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p6-cache.html

    r1779 r1793  
    452452  }
    453453  @bottom-center {
    454        content: "Expires January 15, 2013";
     454       content: "Expires January 16, 2013";
    455455  }
    456456  @bottom-right {
    … …  
    498498      <meta name="dct.creator" content="Reschke, J. F.">
    499499      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    500       <meta name="dct.issued" scheme="ISO8601" content="2012-07-14">
     500      <meta name="dct.issued" scheme="ISO8601" content="2012-07-15">
    501501      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    502502      <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 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.">
    … …  
    524524            </tr>
    525525            <tr>
    526                <td class="left">Expires: January 15, 2013</td>
     526               <td class="left">Expires: January 16, 2013</td>
    527527               <td class="right">M. Nottingham, Editor</td>
    528528            </tr>
    … …  
    541541            <tr>
    542542               <td class="left"></td>
    543                <td class="right">July 14, 2012</td>
     543               <td class="right">July 15, 2012</td>
    544544            </tr>
    545545         </tbody>
    … …  
    570570         in progress”.
    571571      </p>
    572       <p>This Internet-Draft will expire on January 15, 2013.</p>
     572      <p>This Internet-Draft will expire on January 16, 2013.</p>
    573573      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    574574      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    860860         <li>the "no-store" cache directive (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.1" title="Cache-Control">Section&nbsp;7.2</a>) does not appear in request or response header fields, and
    861861         </li>
    862          <li>the "private" cache response directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;7.2.2</a>) does not appear in the response, if the cache is shared, and
     862         <li>the "private" cache response directive (see <a href="#cache-response-directive.private" title="private">Section&nbsp;7.2.2.2</a>) does not appear in the response, if the cache is shared, and
    863863         </li>
    864864         <li>the <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a> header field (see <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>) does not appear in the request, if the cache is shared, unless the response explicitly allows it (see <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a>), and
    … …  
    868868               <li>contains an <a href="#header.expires" class="smpl">Expires</a> header field (see <a href="#header.expires" id="rfc.xref.header.expires.1" title="Expires">Section&nbsp;7.3</a>), or
    869869               </li>
    870                <li>contains a max-age response cache directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;7.2.2</a>), or
     870               <li>contains a max-age response cache directive (see <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.7</a>), or
    871871               </li>
    872872               <li>contains a s-maxage response cache directive and the cache is shared, or</li>
    … …  
    914914         <li>the presented request does not contain the no-cache pragma (<a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section&nbsp;7.4</a>), nor the no-cache cache directive (<a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;7.2.1</a>), unless the stored response is successfully validated (<a href="#validation.model" title="Validation Model">Section&nbsp;4.2</a>), and
    915915         </li>
    916          <li>the stored response does not contain the no-cache cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;7.2.2</a>), unless it is successfully validated (<a href="#validation.model" title="Validation Model">Section&nbsp;4.2</a>), and
     916         <li>the stored response does not contain the no-cache cache directive (<a href="#cache-response-directive.no-cache" title="no-cache">Section&nbsp;7.2.2.3</a>), unless it is successfully validated (<a href="#validation.model" title="Validation Model">Section&nbsp;4.2</a>), and
    917917         </li>
    918918         <li>the stored response is either:
    … …  
    946946      </p>
    947947      <p id="rfc.section.4.1.p.2">The primary mechanism for determining freshness is for an origin server to provide an explicit expiration time in the future,
    948          using either the <a href="#header.expires" class="smpl">Expires</a> header field (<a href="#header.expires" id="rfc.xref.header.expires.2" title="Expires">Section&nbsp;7.3</a>) or the max-age response cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;7.2.2</a>). Generally, origin servers will assign future explicit expiration times to responses in the belief that the representation
     948         using either the <a href="#header.expires" class="smpl">Expires</a> header field (<a href="#header.expires" id="rfc.xref.header.expires.2" title="Expires">Section&nbsp;7.3</a>) or the max-age response cache directive (<a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.7</a>). Generally, origin servers will assign future explicit expiration times to responses in the belief that the representation
    949949         is not likely to change in a semantically significant way before the expiration time is reached.
    950950      </p>
    … …  
    970970      <p id="rfc.section.4.1.1.p.1">A cache can calculate the freshness lifetime (denoted as freshness_lifetime) of a response by using the first match of: </p>
    971971      <ul>
    972          <li>If the cache is shared and the s-maxage response cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;7.2.2</a>) is present, use its value, or
    973          </li>
    974          <li>If the max-age response cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;7.2.2</a>) is present, use its value, or
     972         <li>If the cache is shared and the s-maxage response cache directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.8</a>) is present, use its value, or
     973         </li>
     974         <li>If the max-age response cache directive (<a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.7</a>) is present, use its value, or
    975975         </li>
    976976         <li>If the <a href="#header.expires" class="smpl">Expires</a> response header field (<a href="#header.expires" id="rfc.xref.header.expires.3" title="Expires">Section&nbsp;7.3</a>) is present, use its value minus the value of the <a href="p2-semantics.html#header.date" class="smpl">Date</a> response header field, or
    … …  
    14951495      </p>
    14961496      <div class="note" id="rfc.section.7.3.p.7">
    1497          <p> <b>Note:</b> If a response includes a <a href="#header.cache-control" class="smpl">Cache-Control</a> field with the max-age directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;7.2.2</a>), that directive overrides the Expires field. Likewise, the s-maxage directive overrides Expires in shared caches.
     1497         <p> <b>Note:</b> If a response includes a <a href="#header.cache-control" class="smpl">Cache-Control</a> field with the max-age directive (see <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.7</a>), that directive overrides the Expires field. Likewise, the s-maxage directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.8</a>) overrides the <a href="#header.expires" class="smpl">Expires</a> header fieldin shared caches.
    14981498         </p>
    14991499      </div>
Note: See TracChangeset for help on using the changeset viewer.