On 10/03/21 12:57 am, roee klinger wrote:
Hey,
I have found a lot of outdated or conflicting information about this
online, and since this is a really important matter, I wanted to make
sure I am doing this correctly.
I am attempting to block some websites completely, including all HTTPS
I am currently using:###blocked websites###acl blockedsites dstdomain .domain1.com .domain2.com .domain3.com###end blocked websites###http_access deny blockedsitesSimple and working ;)--Diese Nachricht wurde von meinem Android Mobiltelefon mit WEB.DE Mail gesendet.Am 09.03.21, 12:58 schrieb
On 3/8/21 10:10 AM, Niels Hofmans wrote:
> During testing sslbump + icap I noticed that websockets (ws + was) are
> not supported by squid. (Even if using on_unsupported_protocol)
> Are there any plans for supporting this with sslbump?
Your question can be misinterpreted in many different ways.
Hey,
I have found a lot of outdated or conflicting information about this
online, and since this is a really important matter, I wanted to make sure
I am doing this correctly.
I am attempting to block some websites completely, including all HTTPS
traffic and subdomains.
Squid.conf:
acl
Hello,
can someone test the following URL
http://db.local.clamav.net/daily-26102.cdiff
e.g. wget http://db.local.clamav.net/daily-26102.cdiff
I have an older squid (v3.1) there this works,
but with the newer ones (v3.4 and v3.5) this doesn't;
is there an explanation why?
the log shows
Hi Alex,
Thank you for your response. I’ll be opening up a Bugzilla ticket for opaque
messages through ICAP if it doesn’t exist already.
Related to the squid 5.x, I’ve reached out to the debian package maintainer
last week for a binary install in the repos but no response as of yet.
Best
