Re: [squid-users] ICAP problem in 3.1.18

2012-01-04 Thread Daniel Beschorner
There is also a strange 1-byte body attached. It could be the body pipeline or network I/O functions hung waiting for more data in order to prevent single-byte packets. Amos Hi Amos, exactly this seems to be the point, but in an other way! I think the patch fails to do the contentSize =

Re: [squid-users] ICAP problem in 3.1.18

2012-01-04 Thread Daniel Beschorner
I think the patch fails to do the contentSize = 1 handling correctly, because the bytesWanted call returns ambiguously 0 in case of contentSize = 1. Daniel Filed by another user as http://bugs.squid-cache.org/show_bug.cgi?id=3466 So we can close this here. Thank you! Daniel

[squid-users] ICAP problem in 3.1.18

2012-01-03 Thread Daniel Beschorner
One month ago I reported an ICAP regression in 3.1.17/18. In meantime I tracked down the problem to patch 10403 (Bug 2619). Maybe it helps to find the issue. Thank you Daniel After upgrading to 3.1.18 (+adaption compile patch) the following url = never stops loading in the browser

Re: [squid-users] ICAP problem in 3.1.18

2012-01-03 Thread Amos Jeffries
On 4/01/2012 4:01 a.m., Daniel Beschorner wrote: One month ago I reported an ICAP regression in 3.1.17/18. In meantime I tracked down the problem to patch 10403 (Bug 2619). Maybe it helps to find the issue. Thank you Daniel After upgrading to 3.1.18 (+adaption compile patch) the

[squid-users] icap problem with 3.1.18

2011-12-08 Thread Daniel Beschorner
After upgrading to 3.1.18 (+adaption compile patch) the following url never stops loading in the browser http://x.ligatus.com/cgi-bin/ivw/CP/11260-365/83-1056/129647-107545-_129709-105679-_128565-101085-// If I bypass the ICAP server for this url (which is indeed a redirect to