-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/12/2014 1:27 a.m., Yuri Voinov wrote:
>
> Hm,
>
> I don't think so.
>
> proxy_auth cannot be use on transparent interceptor.
>
> Does it mean, that cachemgr authentification impossible in my
> case?
>
> Or, may be, we have bug there?
You sh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Smear in my hand... :))
I have forgotten to enable basic auth when build
My stupid head :
All ok now.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQEcBAEBAgAGBQJUnx6/AAoJENNXIZxhPexGxIgH/AqTEHdtM2QJdhhGIHLFVsqc
E/AzxoL+aW
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/26/2014 02:22 PM, HackXBack wrote:
> Hello squid , after using 3.5.0.4 on fresh debian system i see many
> errors in cache.log
Hey There,
(leaving aside these errors)
As a part of a cache proxy integration I am generally recommending to
do it i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Yuri,
I am not sure yet how you have tried to access the cachemgr?
The basic settings of squid allow any request throw 127.0.0.1 and the
basic forward proxy port access to cache mgr interface.
If you are using Munin and it cannot access put this a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hm,
I don't think so.
proxy_auth cannot be use on transparent interceptor.
Does it mean, that cachemgr authentification impossible in my case?
Or, may be, we have bug there?
WBR, Yuri
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQEcBAEBAgA
