fre 2010-02-12 klockan 13:40 +1300 skrev Amos Jeffries: > Chris Robertson wrote:
> >> HTTP/1.1 200 OK > >> Accept-Ranges: bytes > >> Cache-Control: max-age=2592000 > >> Content-Type: image/gif > >> Expires: Sat, 13 Mar 10 22:37:08 GMT > >> X-Cnection: close > >> Date: Thu, 11 Feb 2010 22:37:08 GMT > >> Content-Length: 522 > >> > >> General: The Expires header's value isn't a valid date. > > That above is probably the killer. As we get closer to HTTP/1.1 > compliance we get more things discarded for non-compliance. > > Invalid date maps to "-1" and non-cacheable. But even then Cache-Control max-age should have higher priority.. Expires should only be looked at if there is no cc s-maxage/max-age. Regards Henrik
