Hi, The configuration directive pconn_lifetime (http://www.squid-cache.org/Doc/config/pconn_lifetime/), seems to give the squid admin control over whether squid closes idle connections or moves them into the 'idle connection pool'... I am curious if in squid3, the connection was automatically terminated after being idle or if it was automatically moved to the idle connection pool. Given the default value for this config (to always move to the idle connection pool), I assume the default functionality between squid 3 and 4 is the same? I ask because I am seeing a strange, not consistently reproducible scenario where I navigate to an origin through squid (SSL bump), and then after some time if I click on a link that navigates somewhere within the same domain, the browser hangs for a bit until eventually making the navigation. On the squid side, in the logs, I can see that there is an event in the access logs that is "NONE error:transaction-end-before-headers HTTP/0.0" before then seeing the browser issue a fresh CONNECT at which point everything seems to work. It seems like the client is trying to use the same connection, but from the squid side that connection is in a strange state, and so some amount of time transpires before squid deems the connection closed. I can use this pconn_lifetime configuration to 'fix' this problem, but I'm weary of potentially causing some other side effects by too aggressively closing connections? Since this doesn't reproduce in squid3, I thought I would ask if the behavior has changed in anyway in this path.. Thank you for any help, John -- Sent from: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
