Thanks for your quick response... I have also configured, but the value seems not to be honored: connect_timeout 30 seconds The primary peer is down, but Squid does not print any "Dead parent" in the logs. Every HTTPS request is forwarded to the primary peer and it takes 1 minute until the secondary peer gets used, even with "connect_timeout 30 seconds". I think, I am facing the first issue that has been fixed by your patch. Are there any plans to backport this fix to Xenial APT repositories or to create a new Debian package for Squid4/5? Regards, Jens Gesendet: Donnerstag, 16. März 2017 um 06:37 Uhr Von: "Alex Rousskov" <rousskov@xxxxxxxxxxxxxxxxxxxxxxx> An: squid-users@xxxxxxxxxxxxxxxxxxxxx Cc: "Jens Offenbach" <wolle5050@xxxxxx> Betreff: Re: No failover when default parent proxy fails (Squid 3.5.12) On 03/15/2017 11:23 PM, Jens Offenbach wrote: > Failover does not seem to work properly in case of HTTPS. We have recently discovered and fixed two bugs in failure recovery code code for tunneled (not bumped) HTTPS connections: http://lists.squid-cache.org/pipermail/squid-dev/2017-March/008243.html I do not know whether our (not yet officially reviewed) fixes will help in your use case and whether you can try v4 or v5 to test them. HTH, Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
