[squid-users] Experimental YouTube Caching helper\tool and SQUID 3.5.25 + 4.0.19 RPM's RELEASED

Amos Jeffries squid3 at treenet.co.nz
Wed May 17 04:29:12 UTC 2017

On 17/05/17 14:50, Eliezer Croitoru wrote:
> Now I am encountering an issue:
> I worked on the ICAP service and it works fine to find and extract the unique identifier for the googlevideo id prediction.
> Now I have a working ICAP+StoreID helpers but from an unknown reason it seems that squid find's a match in the cache but still serves the content from the origin server.
> What might be causing it?

There are three possible reasons visible in the server response:

1) private response
  Cache-Control: private

2) stale response
  Last-Modified: Wed, 08 Apr 2015 09:25:11 GMT
  Cache-Control: max-age=21292

3) stale response
   Date: Wed, 17 May 2017 02:00:24 GMT
   Expires: Wed, 17 May 2017 02:00:24 GM

and another in the Squid backend request:
   Cache-Control: max-age=4794000

That means that either;
  a) the refresh_pattern has been configured to force objects to be 
under 55.4 days to avoid revalidation
  b) the object in cache is 55.4 days old and Squid is seeking an update.

Except there are no If-* headers to indicate revalidation, so probably (a).

In either case the server is responding with an object which is both a 
full-size 200 status, and already over 2 years old:
   Last-Modified: Wed, 08 Apr 2015 09:25:11 GMT
so the new object already cannot meet the freshness requirements before 
it is even delivered to Squid.

Currently Squid caches such responses and uses them in favour of older 
cached content, especially when Store-ID is obscuring the exact URL 
origin of the older content.


More information about the squid-users mailing list