On 16/03/2016 11:52 p.m., joe wrote: > is this cachable > The headers say it _might_ be. Response headers are not the whole story though. Request headers matter. As do *all* of your refresh_pattern lines. > > HTTP/1.1 200 OK > Accept-Ranges: bytes > Content-Type: video/x-flv > Server: nginx > Cache-Control: public, public > Age: 5707758 > Date: Wed, 16 Mar 2016 11:15:20 GMT > Last-Modified: Thu, 21 May 2015 14:56:19 GMT > Expires: Mon, 09 May 2016 09:46:02 GMT > Content-Length: 22371738 > X-Cache: MISS from proxy.net > Connection: keep-alive > > refresh_pattern -i \.(flv|mp4|3gp|jpg) 129600 100% 129600 override-expire > ignore-reload ignore-no-store ignore-must-revalidate ignore-private > ignore-auth store-stale > > i see Cache-Control: public, public <--- double dose that affect not > to cache ?? "public" has no meaning at all on non-Authenticated traffic. That header is effectively empty. *Assuming* that refresh_pattern actually is the one being used for that response: Expires: May 2016 -> still fresh and cacheable but; administrative override refresh_pattern override-expires -> cancel Expires result L-M factor algorithm -> 1.0 x (Date - LM + Age) = fresh for 31704499s -> limit of (129600 x 60) = fresh for 7776000s -> fresh for 7776000 seconds (90 days) Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
