Ignore:
Timestamp:
Aug 8, 2011, 12:37:45 PM (8 years ago)
Author:
fielding@…
Message:

Be intolerant. Move cache date requirements hiding in appendix to p6.

File:
1 edited

Legend:

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

    r1376 r1390  
    869869  current_age = corrected_initial_age + resident_time;
    870870</artwork></figure>
     871<t>
     872   Additional rules for requirements on parsing and encoding of dates
     873   and other potential problems with date encodings include:
     874</t>
     875<t>
     876  <list style="symbols">
     877     <t>HTTP/1.1 clients and caches &SHOULD; assume that an RFC-850 date
     878        which appears to be more than 50 years in the future is in fact
     879        in the past (this helps solve the "year 2000" problem).</t>
     880
     881     <t>Although all date formats are specified to be case-sensitive,
     882        recipients &SHOULD; match day, week and timezone names
     883        case-insensitively.</t>
     884             
     885     <t>An HTTP/1.1 implementation &MAY; internally represent a parsed
     886        Expires date as earlier than the proper value, but &MUST-NOT;
     887        internally represent a parsed Expires date as later than the
     888        proper value.</t>
     889
     890     <t>All expiration-related calculations &MUST; be done in GMT. The
     891        local time zone &MUST-NOT; influence the calculation or comparison
     892        of an age or expiration time.</t>
     893
     894     <t>If an HTTP header field incorrectly carries a date value with a time
     895        zone other than GMT, it &MUST; be converted into GMT using the
     896        most conservative possible conversion.</t>
     897  </list>
     898</t>
    871899</section>
    872900
Note: See TracChangeset for help on using the changeset viewer.