On 2024-09-25 01:57, にば wrote:
We then added the following settings that were in the existing Squid proxy
# SSL_BUMP
acl allowed_https_sites ssl::server_name "/etc/squid/whitelist"
acl allowed_https_sites ssl::server_name "/etc/squid/whitelist_transparent"
acl allowed_https_sites ssl::server_na
Thanks Jeffries
Jonathan Lee
Sent from my iPhone
> On Oct 3, 2024, at 01:07, Amos Jeffries wrote:
>
> On 2/10/24 05:05, Jonathan Lee wrote:
>> Hello fellow squid users,
>> Can you please help? I am attempting to run wpad on the same machine as
>> squid however port 80 443 is blocked, I have
On 10/2/24 23:30, Alex Rousskov wrote:
Disadvantages of using eCAP+ClamAV adapter include being dependent on a
relatively old libecap and ClamAV eCAP adapter implementation.
Ah!
I got it all wrong then... I thought ICAP was older and eCAP was meant
to replace it.
Thanks for clarifying.
I
On 2024-10-03 10:12, Andrea Venturoli wrote:
On 10/2/24 23:30, Alex Rousskov wrote:
Disadvantages of using eCAP+ClamAV adapter include being dependent on
a relatively old libecap and ClamAV eCAP adapter implementation.
I got it all wrong then... I thought ICAP was older and eCAP was meant
to
Hello.
I've got several machines with the following software:
FreeBSD 13.3, 13.4 or 14.1
Squid 6.10
c-icap 0.5.12
SquidClamav 7.3
ClamA: 1.3.2
This combination usually works pretty well, but it occasionally chokes,
with the client seeing:
ICAP protocol error
The system returned: [No Error]
O
On 2024-10-03 11:10, Andrea Venturoli wrote:
> Out of 10 installations, ... on one it's very frequent.
> Any idea on what to check or try? ... Any way to get better logs?
Since the problem is frequent on that one host, I recommend privately
sharing[1] a pointer to compressed debugging cache.lo
On 10/3/24 18:29, Alex Rousskov wrote:
Since the problem is frequent on that one host, I recommend privately
sharing[1] a pointer to compressed debugging cache.log collected while
> ...
I'll try ASAP.
It is enough to record one or two problematic cases.
If only it was so easy to know in
