Hi everyone,
I'm using Squid 4.14 for windows and I've tried the ldap authentification by
using :
Basic_ldap_auth.exe
Basic_ncsa.auth.exe
Digest_ldap_auth.exe
Ext_ldap_auth.exe
When I start my squid service for windows, I get the following cache.log
2021/09/29 16:40:57| Created PID file (/var/
Ok, it seems this whole squid proxy thing went down the FUBAR route faster than
I could redirect to dev/null.
Apparently Debian/Ubunutu does not support openSSL anymore and uses GnuTLS
whatever that thing is. Once again I feel savaged by "systemd". I knew, when I
started the new job that it will
On 9/29/21 8:46 AM, robert k Wild wrote:
> hi all,
>
> going by this link
>
> https://wiki.squid-cache.org/ConfigExamples/ContentAdaptation/C-ICAP
>
> theres two icap configuration options, what one should i use
The answer depends on what you are using c-icap for:
* If you want to adapt (inclu
hi all,
going by this link
https://wiki.squid-cache.org/ConfigExamples/ContentAdaptation/C-ICAP
theres two icap configuration options, what one should i use as atm i have
this in my squid.conf
#ICAP
icap_enable on
adaptation_uses_indirect_client on
icap_send_client_ip on
icap_send_client_userna
Thanks for the quick input and the hint.
We don't use CentOS at work but I am using it on my workstation so that was a
nice hint.
The more I read abut ufdbGuard the more I am angry on myself for struggling
with the squidguard extension for so long. Should have done it from scratch in
the first p
