Re: tracking maxconn between several haproxy server definitions - which correspond to same real web server

Hi, Thanks for you replies, please see comment below. On 10/31/2011 10:45 PM, Baptiste wrote: Hi, If cookie insert is not an option, Hmm ... in general when would a cookie insert be a bad/no option compared to appsession or cookie persistence learning available in 1.5 ? For me the obvious

Re: tracking maxconn between several haproxy server definitions - which correspond to same real web server

Hi, Le Lundi 31 Octobre 2011 17:21:02 Piavlo a écrit : I have been using *capture cookie* and *appsession *in one haproxy configuration for sticky sessions. The problem is that then haproxy restarted/reload or domain is migrated to failover server the sticky data is lost. Today I realised

Re: tracking maxconn between several haproxy server definitions - which correspond to same real web server

Hi, If cookie insert is not an option, then in 1.5-dev7, you can perform cookie persistence learning the application cookie and store it in a stick table. It's like appsession, unless it will survive a reload and you can share it between HAProxy boxes. :) cheers On Mon, Oct 31, 2011 at 7:40 PM,