Ignore:
Timestamp:
May 6, 2013, 11:17:49 PM (7 years ago)
Author:
mnot@…
Message:

Move date parsing advice up to freshness; see #469

File:
1 edited

Legend:

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

    r2234 r2235  
    579579</t>
    580580<t>
     581   When calculating freshness, to avoid common problems in date parsing:
     582</t>
     583<t>
     584  <list style="symbols">
     585     <t>Although all date formats are specified to be case-sensitive,
     586        cache recipients &SHOULD; match day, week and timezone names
     587        case-insensitively.</t>
     588             
     589     <t>If a cache recipient's internal implementation of time has less
     590        resolution than the value of an HTTP-date, the recipient &MUST;
     591        internally represent a parsed <x:ref>Expires</x:ref> date as the
     592        nearest time equal to or earlier than the received value.</t>
     593
     594     <t>Cache recipients &MUST-NOT; allow local time zones to influence the
     595        calculation or comparison of an age or expiration time.</t>
     596
     597     <t>Cache recipients &SHOULD; consider a date with a zone abbreviation
     598        other than "GMT" to be invalid for calculating expiration.</t>
     599  </list>
     600</t>
     601<t>
    581602   Note that freshness applies only to cache operation; it cannot be used to
    582603   force a user agent to refresh its display or reload a resource. See <xref
     
    761782  current_age = corrected_initial_age + resident_time;
    762783</artwork></figure>
    763 <t>
    764    Additionally, to avoid common problems in date parsing:
    765 </t>
    766 <t>
    767   <list style="symbols">
    768      <t>Although all date formats are specified to be case-sensitive,
    769         cache recipients &SHOULD; match day, week and timezone names
    770         case-insensitively.</t>
    771              
    772      <t>If a cache recipient's internal implementation of time has less
    773         resolution than the value of an HTTP-date, the recipient &MUST;
    774         internally represent a parsed <x:ref>Expires</x:ref> date as the
    775         nearest time equal to or earlier than the received value.</t>
    776 
    777      <t>Cache recipients &MUST-NOT; allow local time zones to influence the
    778         calculation or comparison of an age or expiration time.</t>
    779 
    780      <t>Cache recipients &SHOULD; consider a date with a zone abbreviation
    781         other than "GMT" to be invalid for calculating expiration.</t>
    782   </list>
    783 </t>
    784784</section>
    785785
Note: See TracChangeset for help on using the changeset viewer.