[squid-users] cache_peer name gone from logs after upgrade to 3.5
Daniel Sutcliffe
dans at chairfour.com
Wed Sep 28 17:48:12 UTC 2016
I have been using squid 3.1 on EL6 for a long time and recently made
the upgrade to 3.5 - all seems to be working as expected functionality
wise, but I'm noticing a difference in the log file content which is
not helping me doing a bit of peer debugging...
In 3.1 the access.log used to contain a:
*_PARENT/<peername>
What I'm now seeing is:
*_PARENT/<peer-ip>
Which wouldn't be so bad if all my <peer-ip> are the same, 127.0.0.1
as they are all SSH tunnels.
Otherwise the cache_peer name= directive seems to be doing its job as
far as ACLs are concerned.
Maybe this is now the expected behavior but I can't seem to find it
documented anywhere - it would be nice if the old log behavior could
be turned back on or I could have it confirmed that what I am seeing
is just the way it is now.
Cheers
/dan
--
Daniel Sutcliffe <dans at chairfour.com>
Chair Four Development Group LLC
More information about the squid-users
mailing list