Changeset 1484


Ignore:
Timestamp:
Dec 4, 2011, 7:25:08 PM (8 years ago)
Author:
mnot@…
Message:

Refine age calculation for 1.1 proxy chains (#212).

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

Legend:

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

    r1483 r1484  
    978978  corrected_age_value = age_value + response_delay; 
    979979</pre> <div id="rfc.figure.u.6"></div>
    980       <p>These are combined as</p>  <pre class="text">  corrected_initial_age = max(apparent_age, corrected_age_value);
    981 </pre><p id="rfc.section.2.3.2.p.11">The current_age of a stored response can then be calculated by adding the amount of time (in seconds) since the stored response
     980      <p>These <em class="bcp14">SHOULD</em> be combined as
     981      </p>  <pre class="text">  corrected_initial_age = max(apparent_age, corrected_age_value);
     982</pre><p id="rfc.section.2.3.2.p.11">unless the cache is confident in the value of the Age header (e.g., because there are no HTTP/1.0 hops in the Via header),
     983         in which case the corrected_age_value <em class="bcp14">MAY</em> be used as the corrected_initial_age.
     984      </p>
     985      <p id="rfc.section.2.3.2.p.12">The current_age of a stored response can then be calculated by adding the amount of time (in seconds) since the stored response
    982986         was last validated by the origin server to the corrected_initial_age.
    983987      </p>
    984988      <div id="rfc.figure.u.7"></div><pre class="text">  resident_time = now - response_time;
    985989  current_age = corrected_initial_age + resident_time;
    986 </pre><p id="rfc.section.2.3.2.p.13">Additionally, to avoid common problems in date parsing:</p>
    987       <p id="rfc.section.2.3.2.p.14"> </p>
     990</pre><p id="rfc.section.2.3.2.p.14">Additionally, to avoid common problems in date parsing:</p>
     991      <p id="rfc.section.2.3.2.p.15"> </p>
    988992      <ul>
    989993         <li>HTTP/1.1 clients and caches <em class="bcp14">SHOULD</em> assume that an RFC-850 date which appears to be more than 50 years in the future is in fact in the past (this helps solve
     
    20992103         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/293">http://tools.ietf.org/wg/httpbis/trac/ticket/293</a>&gt;: "Interaction of request and response Cache-Control"
    21002104         </li>
     2105         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/212">http://tools.ietf.org/wg/httpbis/trac/ticket/212</a>&gt;: "Refining age for 1.1 proxy chains"
     2106         </li>
    21012107      </ul>
    21022108      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r1483 r1484  
    880880</figure>
    881881<figure>
    882 <preamble>These are combined as</preamble>
     882<preamble>These &SHOULD; be combined as</preamble>
    883883<artwork type="code">
    884884  corrected_initial_age = max(apparent_age, corrected_age_value);
    885885</artwork></figure>
     886<t>
     887   unless the cache is confident in the value of the Age header (e.g., because
     888   there are no HTTP/1.0 hops in the Via header), in which case the
     889   corrected_age_value &MAY; be used as the corrected_initial_age.</t>
    886890<t>
    887891   The current_age of a stored response can then be calculated by adding the
     
    29382942      "Interaction of request and response Cache-Control"
    29392943    </t>
     2944    <t>
     2945      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/212"/>:
     2946      "Refining age for 1.1 proxy chains"
     2947    </t>
    29402948  </list>
    29412949</t>
Note: See TracChangeset for help on using the changeset viewer.