Thanks Amos
You means using "login=PASS" in peer settings and in Proxy parent B and
C use the "basic_fake_auth" helper to "simulate" the requested auth ?
Le 17/11/2020 à 11:43, Amos Jeffries a écrit :
On 17/11/20 9:27 pm, David Touzeau wrote:
Hi,
We a first Squid using Kerberos +
Hello Amos,
I am using the latest squid release on alpine, which is 4.13-r0.
After using the exact command openssl req -new -newkey rsa:2048 -sha256 -days
365 -nodes -x509 -extensions v3_ca -keyout ca.pem -out ca.pem I still receive
this error.
Since it’s a debug cert, I gisted it here:
Hi,
After noticing my permission errors on /ca.pem, I more or less got this:
Is /dev/log/ really required, since we log to /dev/stdout?
proxy_1 | [00] open("/dev/stdout", O_RDWR|O_CREAT|O_APPEND, 0666) = -1
EACCES (Permission denied)
proxy_1 | [00] writev(2, [{iov_base="WARNING:
On Wednesday, November 4, 2020, 3:27:25 AM GMT+1, Alex Rousskov
wrote:
> https://bugs.squid-cache.org/show_bug.cgi?id=5084
Hi,
I added a comment to that bug report.
I cannot reproduce the problem anymore, at least not with the latest version of
Squid 5.
Thanks,
Vieri
On 11/18/20 3:20 PM, robert k Wild wrote:
> can i use the acl "reply_header_access" to block downloads, like i have
> done with the " rep_mime_type " or is this not what its meant for
Roughly speaking, ACL is a boolean function -- something that gives
Squid a yes/no answer to an ACL-specific
