Thanks Amos - So then it more than likely is related to our external ACLs that deal with the HTTP response? > On 20 Feb 2015, at 5:06 pm, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: > > On 20/02/2015 5:46 p.m., Eliezer Croitoru wrote: >> Hey Dan, >> >> The basic rule of thumb in programming lands is script vs compiled code. >> Where compiled code can be considered very reliable and in most cases >> tested much more then scripts. >> I am fearing that there is some race between all sorts of things on >> runtime which might lead to this failed test. >> >> There are couple possibilities that can cause the issue you are writing >> about. >> From the compiled side of the code the main suspect is that the >> connection got into a "non usable" state before squid could do something >> else. >> I have not seen yet the source code for connIsUsable but if you wish I >> can try and look at the function\method\call\code source and start a >> basic lookup to understand the issue a bit more. > > Its a simple test to check to ensure the client connection is open when > writing some response data to it. > > Something has earlier cause client connection closure, and something > else earlier has failed to cleanup the state or check the state was sane > before getting to the point of assertion. > > Amos > > _______________________________________________ > squid-users mailing list > squid-users@xxxxxxxxxxxxxxxxxxxxx > http://lists.squid-cache.org/listinfo/squid-users _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
