<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">
<div dir="auto"> I wanted to note that since these are BMCs they require basic auth headers to return their response. I noticed that the ignore-auth option was removed awhile ago. Is my only option to go back to Squid 3.5 ?<br />
<br />
TIA,</div>
</div>
<div name="messageSignatureSection"><br />
Bryan Seitz</div>
<div name="messageReplySection">On Oct 11, 2024 at 4:17 AM -0400, Amos Jeffries <squid3@treenet.co.nz>, wrote:<br />
<blockquote type="cite">On 11/10/24 11:08, Bryan Seitz wrote:<br />
<blockquote type="cite" style="border-left-color: grey; border-left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left: 10px;">I removed the header mods and changed the refresh pattern to:<br />
<br />
refresh_pattern . 15 20% 1800 override-expire<br />
ignore-no-cache ignore-no-store ignore-private<br />
<br />
And I always get TCP_MISS. Any other thoughts?<br /></blockquote>
<br />
Ah, I believe it would be best to get a baseline of what Squid default<br />
behaviour is like in your environment. So we can identify what/how you<br />
need to improve it.<br />
<br />
<br />
Firstly, FYI; this is what those controls **actually** do in current<br />
Squid ..<br />
<br />
* override-expires ... forces Squid to handle all responses to act as<br />
if they received "Cache-Control: max-age=900" (15 min) ... store, but<br />
revalidate 180+ seconds (20% of 15min) later.<br />
Result: Anything that could cache longer than 15min becomes a<br />
REFRESH_MISS or MISS, instead of HIT.<br />
Squid default: **do** cache. Revalidate<br />
* after("Date"+"CC: max-age=N") timestamp, otherwise<br />
* after "Expires" timestamp, otherwise<br />
* after ("Date" +1800 minutes) timestamp.<br />
<br />
* ignore-no-cache ... the standardized "CC: no-cache" is badly named,<br />
it tells Squid what **can** be cached.<br />
Result: Squid will discard many stored objects and perform a MISS<br />
instead.<br />
Squid default: **do** cache "CC:private" responses, revalidate on<br />
HIT. Log as REFRESH.<br />
<br />
* ignore-no-store ... force everything marked "CC: no-store" to be stored.<br />
Result: cache fills with non-reusable objects. Leaving not much room<br />
for actual HIT objects.<br />
Squid default: store only objects with can result in more HITs.<br />
<br />
* ignore-private ... force everything with "CC: private" to be discarded.<br />
Result: same as "ignore-no-store".<br />
Squid default: **do** cache "CC:private" responses, revalidate on HIT.<br />
<br />
Note that both HIT and REFRESH mean the object **was** cached.<br />
<br />
<br />
You said that the access.log now contains MISS. Would that be just<br />
"MISS" or "REFRESH" + "MISS" (actually a HIT, but a new object was given<br />
by the server and replaced the pre-stored object).<br />
<br />
<br />
Can you show a pair of request headers from the client, with matching<br />
response from the server? You can use "debug_options 11,2" in recent<br />
Squid versions to get a cache.log trace of the HTTP transactions.<br />
<br />
That might help us spot something more specific. The config change makes<br />
the earlier given ones obsolete.<br />
<br />
<br />
HTH<br />
Amos<br />
<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>