Ok Amos, thanks a lot for your help.
I'll try to update my Squid version i order to block the given domains in my access.log file.
Greetings !!!
El vie., 3 ene. 2020 a las 3:15, Amos Jeffries (<squid3@xxxxxxxxxxxxx>) escribió:
On 3/01/20 7:09 am, Roberto Carna wrote:
> Dear Amos, I have this log entries that I want to disable:
>
> 1577988384.248 0 10.88.1.112 TAG_NONE/503 0 CONNECT
> hangouts.google.com:443 <http://hangouts.google.com:443> fchop HIER_NONE/- -
> 1577988384.435 0 10.88.1.31 TAG_NONE/503 0 CONNECT
> hangouts.google.com:443 <http://hangouts.google.com:443> ccardiff
> HIER_NONE/- -
> 1577988384.659 0 10.88.1.26 TAG_NONE/503 0 CONNECT
> hangouts.google.com:443 <http://hangouts.google.com:443> mtowers
> HIER_NONE/- -
> 1577988385.069 3 10.88.1.13 TAG_NONE/503 0 CONNECT
> hangouts.google.com:443 <http://hangouts.google.com:443> pmonkey
> HIER_NONE/- -
>
> Is it possible doing that using "dstdomain" ???
It should be, but yes you have hit a bug. It may be fixed in the latest
Squid version, but I am not certain of that.
>
> Or maybe squidguard doesn't let do it ?
>
squidguard does not have anything to do with the logging issue.
It likely does have something to do with those being 503 though. It is
responsible for telling Squid what URL to send the upstream server - and
a CONNECT tunnel has no such URL, squidguard cannot handle that.
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users