Hi! Thanks for your reply. I have tried to build squid 3.2 with patch already in separate dir and copied ext_session_acl in my squid 3.1 installation for using it instead squid_session. Results were the same as with old configuration. Nothing changed. 2012/2/24 Amos Jeffries <squid3@xxxxxxxxxxxxx>: > On 24/02/2012 11:26 a.m., Andrew Beverley wrote: >> >> On Fri, 2012-02-24 at 02:06 +0400, Vyacheslav Maliev wrote: >>> >>> Hi! >>> I configured my splash like described here: >>> http://wiki.squid-cache.org/ConfigExamples/Portal/Splash. I have >>> chosen second example (Active Mode) and adopted it to my squid 3.0 >>> version (there is squid_session helper instead ext_session_acl). So >>> when i go to matched URL session is not starting. Only after i go to >>> matched URL and do squid -k reconfigure everything goes well. >>> >>> Is there any method to renew squid automatically? >> >> You are possibly experiencing a bug with the session helper that means >> it does not synchronise correctly between squid workers. The patch >> discussed in the following thread fixes that. Regardless of whether this >> is your problem, you should really use a version that includes the patch >> anyway, but I'm not sure if it was back-ported to any 3.0 versions. > > > It was not. The 3.0 series is no longer maintained for anything beyond major > security vulnerabilities. > > Vyacheslav, please consider an upgrade. At worst-case you can build the > 3.1.19 sources, and copy the squid_session helper built there into your 3.0 > system. It should be a drop-in replacement. > > Amos
