On Wednesday 05 February 2014 11:05:55 Amos Jeffries wrote: > On 2014-02-05 07:38, Hussam Al-Tayeb wrote: > > same thing happens with > > http://cdn.static6.opensubtitles.org/gfx/thumbs/5/1/2/3/2193215.jpg > > > > it generates an warning: > > Warning: 113 SERV1 (squid) This cache hit is still fresh and more > > > > than 1 > > day old > > > > > > Any way to tell squid not to cache objects that would generate this > > warning? > > You want to discard everything over 24hrs old out of your cache? > > That URL headers says: > Date: Tue, 04 Feb 2014 21:57:39 GMT > Expires: Sat, 01 Mar 2014 09:30:32 GMT > Cache-Control: max-age=2592000 > Last-Modified: Fri, 27 Sep 2013 00:49:39 GMT > Age: 476436 > > The object is cacheable up until March, and is currently older than > 24hrs (5.5 days > 1 day). Like Squid is reporting "still fresh and older > than 1 day". One of the strange little mandatory behaviors in RFC 2616 > is adding that Warning. > > Amos I suppose I an just having a hard time understanding the warning. Is it because 5.5 days is more recent than the "Last-Modified in 2013"?
Attachment:
signature.asc
Description: This is a digitally signed message part.
