<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">
<div dir="auto">Still no hits with:<br />
<br />
refresh_pattern . 0 20% 4320 ignore-private reload-into-ims<br />
debug_options 11,2<br />
<br />
Cache log: https://p.bsd-unix.net/?32d7b024a87ab761#Bo4xhz1NVZmPffosydDV61Wp533wqTxcW8C4iFT4oaQ<br />
Store log: https://p.bsd-unix.net/?884a46ba914bf600#HDqP2Hdt68DmhSyHEDvdxxndJNBioqGM6Fe1fsENWWug<br />
<br />
If I am missing debug lmk. Still to note, these servers require basic auth. I saw Squid 3.5 had ignore-auth but it was removed for 4. Is that my issue ?</div>
</div>
<div name="messageSignatureSection"><br />
Bryan Seitz</div>
<div name="messageReplySection">On Oct 13, 2024 at 12:32 AM -0400, Amos Jeffries <squid3@treenet.co.nz>, wrote:<br />
<blockquote type="cite"><br />
Okay, I am seeing the server response is marked "private" and 7hrs old<br />
(25200sec).<br />
<br />
Replacing the Cache-Control header using "max-age=1800" is not having<br />
noticeable effect because 25200sec is already past the 1800sec limit.<br />
<br />
<br />
What you need to do there instead is:<br />
<br />
1) remove the config changing Cache-Control header.<br />
<br />
2) modify the "refresh_pattern . " line to be this:<br />
<br />
refresh_pattern . 0 20% 4320 ignore-private reload-into-ims<br />
<br />
<br />
Your Squid should then cache the server response and treat the "private"<br />
as if it were a "must-revalidate".<br />
<br />
<br />
Please do that then provide a new cache.log trace for us to see how the<br />
server handles a revalidation check.<br />
<br />
<br />
Amos<br />
<br />
_______________________________________________<br />
squid-users mailing list<br />
squid-users@lists.squid-cache.org<br />
https://lists.squid-cache.org/listinfo/squid-users<br /></blockquote>
</div>
</body>
</html>