On 10/17/2014 8:24 am, daniel.rie...@gmx.net wrote:
Hello,
Each of the parents are used for both HTTP & HTTPS in this
configuration, the dead parent detected log message isn't going to be
repeated twice as its one parent, Regardless of which method the
traffic
is passing.
yes, that's correc
Hello,
> Each of the parents are used for both HTTP & HTTPS in this
> configuration, the dead parent detected log message isn't going to be
> repeated twice as its one parent, Regardless of which method the traffic
> is passing.
yes, that's correct, I agree, each peer is used for both HTTP & H
On 10/17/2014 7:23 am, daniel.rie...@gmx.net wrote:
Hello,
I've testet with Squid 3.3.8 and here it is working as expected...
Thanks Amos!
squid.conf:
http_port 3128
http_access allow all
never_direct allow all
cache_peer 10.0.0.101 parent 3128 0 name=TEST1
cache_peer 10.0.0.102 parent 3128 0 n
Hello,
I've testet with Squid 3.3.8 and here it is working as expected...
Thanks Amos!
squid.conf:
http_port 3128
http_access allow all
never_direct allow all
cache_peer 10.0.0.101 parent 3128 0 name=TEST1
cache_peer 10.0.0.102 parent 3128 0 name=TEST2
HTTPS Traffic is sent to first parent (10.0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/10/2014 3:35 a.m., daniel.rie...@gmx.net wrote:
> Hi guys,
>
> I got a problem with DEAD Parent detection. I've configured 2
> parents in squid.conf:
>
> cache_peer 10.0.0.101 parent 3128 0 default name=TEST1 cache_peer
> 10.0.0.102 parent 3128
Hi guys,
I got a problem with DEAD Parent detection.
I've configured 2 parents in squid.conf:
cache_peer 10.0.0.101 parent 3128 0 default name=TEST1
cache_peer 10.0.0.102 parent 3128 0 name=TEST2
So when the first parent isn't reachable, squid detects this (Detected DEAD
Parent: TEST1) and is u