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)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • 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.