Ignore:
Timestamp:
Jul 5, 2012, 8:51:34 PM (7 years ago)
Author:
julian.reschke@…
Message:

add advice on how to treat multiple instances of freshness information (see #353)

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

Legend:

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

    r1727 r1731  
    452452  }
    453453  @bottom-center {
    454        content: "Expires January 6, 2013";
     454       content: "Expires January 7, 2013";
    455455  }
    456456  @bottom-right {
     
    494494      <meta name="dct.creator" content="Reschke, J. F.">
    495495      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    496       <meta name="dct.issued" scheme="ISO8601" content="2012-07-05">
     496      <meta name="dct.issued" scheme="ISO8601" content="2012-07-06">
    497497      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    498498      <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.">
     
    520520            </tr>
    521521            <tr>
    522                <td class="left">Expires: January 6, 2013</td>
     522               <td class="left">Expires: January 7, 2013</td>
    523523               <td class="right">M. Nottingham, Editor</td>
    524524            </tr>
     
    537537            <tr>
    538538               <td class="left"></td>
    539                <td class="right">July 5, 2012</td>
     539               <td class="right">July 6, 2012</td>
    540540            </tr>
    541541         </tbody>
     
    567567         in progress”.
    568568      </p>
    569       <p>This Internet-Draft will expire on January 6, 2013.</p>
     569      <p>This Internet-Draft will expire on January 7, 2013.</p>
    570570      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    571571      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    959959      </ul>
    960960      <p id="rfc.section.2.3.1.p.2">Note that this calculation is not vulnerable to clock skew, since all of the information comes from the origin server.</p>
     961      <p id="rfc.section.2.3.1.p.3">When there is more than one value present for a given directive (e.g., two Expires header fields, multiple Cache-Control:
     962         max-age directives), it is considered invalid. Caches are encouraged to consider responses that have invalid freshness information
     963         to be stale.
     964      </p>
    961965      <h4 id="rfc.section.2.3.1.1"><a href="#rfc.section.2.3.1.1">2.3.1.1</a>&nbsp;<a id="heuristic.freshness" href="#heuristic.freshness">Calculating Heuristic Freshness</a></h4>
    962966      <p id="rfc.section.2.3.1.1.p.1">If no explicit expiration time is present in a stored response that has a status code whose definition allows heuristic freshness
     
    20442048         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/307">http://tools.ietf.org/wg/httpbis/trac/ticket/307</a>&gt;: "untangle Cache-Control ABNF"
    20452049         </li>
     2050         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/353">http://tools.ietf.org/wg/httpbis/trac/ticket/353</a>&gt;: "Multiple values in Cache-Control headers"
     2051         </li>
    20462052         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/355">http://tools.ietf.org/wg/httpbis/trac/ticket/355</a>&gt;: "Case sensitivity of header fields in CC values"
    20472053         </li>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r1727 r1731  
    672672   the information comes from the origin server.
    673673</t>
     674<t>
     675   When there is more than one value present for a given directive (e.g., two
     676   Expires header fields, multiple Cache-Control: max-age directives), it is
     677   considered invalid. Caches are encouraged to consider responses that have
     678   invalid freshness information to be stale.
     679</t>
    674680
    675681<section anchor="heuristic.freshness" title="Calculating Heuristic Freshness">
     
    26012607    </t>
    26022608    <t>
     2609      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/353"/>:
     2610      "Multiple values in Cache-Control headers"
     2611    </t>
     2612    <t>
    26032613      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/355"/>:
    26042614      "Case sensitivity of header fields in CC values"
Note: See TracChangeset for help on using the changeset viewer.