On 01/18/2007 12:49 PM, Henrik Nordstrom wrote: > tor 2007-01-18 klockan 12:05 +0100 skrev Plüm, Rüdiger, VF EITO:
> > Any valid date which can be represented in the textual form is a valid > Expires header. And any Expires header you can not understand for > whatever reason is "already expired in the past". > > To solve this there is Cache-Control max-age which is not sensitive to > the limits of your internal time representation, and which overrides > Expires if present. Just trying to clarify: So if we have (an Expires header in the past *OR* a broken Expires header) *AND* (a max-age > 0 *AND* a s-max-age not present ) *OR* (a s-max-age > 0 *AND* (max-age >= 0 *OR* max-age not present))) we should cache it (provided nothing else in Cache-Control does restrict that)? Regards Rüdiger
