Hi there,I've upgraded Squid to 3.1.14.xx, problem is solved (checked on two proxy servers). Third will be replaced within 2 months, so I don't upgrade Squid now.
Thanks and best regards J.K. Cituji Amos Jeffries <squid3@xxxxxxxxxxxxx>:
On 29/07/11 00:05, Josef Karliak wrote:Hi and thank for your reply, but there is no progress... detect_broken_pconn if off by default squid config, but it was enabled by default suse config. I've disable it - no progress. Do you've any ideas ? I'll email to oki.cz of course ... Thanks Best regards J.Karlia.Other than report it there is nothing you can actually do. Hopefully it is not a big impact problem. Just another thing dropping connections before they can be re-used.The actual transfer has been successful this is only a problem with the persistent connection reuse (and indirectly with things like NTLM auth which rely on pconn protecting against the load).Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.14 Beta testers wanted for 3.2.0.10
--Ma domena pouziva zabezpeceni a kontrolu SPF (www.openspf.org) a DomainKeys/DKIM (with ADSP) . Pokud mate problemy s dorucenim emailu, zacnete pouzivat metody overeni puvody emailu zminene vyse. Dekuji. My domain use SPF (www.openspf.org) and DomainKeys/DKIM (with ADSP) policy and check. If you've problem with sending emails to me, start using email origin methods mentioned above. Thank you.
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Attachment:
binELxNdWAVoN.bin
Description: =?iso-8859-2?b?VmX4ZWpu/Q==?= PGP =?iso-8859-2?b?a2zt6A==?=
