One of the endpoints on these BMCs does not require auth and Squid is caching that. It will not cache the endpoints that require auth. I want it to do this, is there a way? (This is literally for metrics, not private data)
Bryan Seitz On Oct 14, 2024 at 2:35 PM -0400, Bryan Seitz <seit...@gmail.com>, wrote: > Still no hits with: > > refresh_pattern . 0 20% 4320 ignore-private reload-into-ims > debug_options 11,2 > > Cache log: > https://p.bsd-unix.net/?32d7b024a87ab761#Bo4xhz1NVZmPffosydDV61Wp533wqTxcW8C4iFT4oaQ > Store log: > https://p.bsd-unix.net/?884a46ba914bf600#HDqP2Hdt68DmhSyHEDvdxxndJNBioqGM6Fe1fsENWWug > > 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 ? > > Bryan Seitz > On Oct 13, 2024 at 12:32 AM -0400, Amos Jeffries <squ...@treenet.co.nz>, > wrote: > > > > Okay, I am seeing the server response is marked "private" and 7hrs old > > (25200sec). > > > > Replacing the Cache-Control header using "max-age=1800" is not having > > noticeable effect because 25200sec is already past the 1800sec limit. > > > > > > What you need to do there instead is: > > > > 1) remove the config changing Cache-Control header. > > > > 2) modify the "refresh_pattern . " line to be this: > > > > refresh_pattern . 0 20% 4320 ignore-private reload-into-ims > > > > > > Your Squid should then cache the server response and treat the "private" > > as if it were a "must-revalidate". > > > > > > Please do that then provide a new cache.log trace for us to see how the > > server handles a revalidation check. > > > > > > Amos > > > > _______________________________________________ > > squid-users mailing list > > squid-users@lists.squid-cache.org > > https://lists.squid-cache.org/listinfo/squid-users
_______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org https://lists.squid-cache.org/listinfo/squid-users
