On 26/03/2013 10:11, Baptiste wrote:
Hi Christophe,
This issue should not happen.
Please share your backend configuration here.
Baptiste
Could this not occur in an instance where cookies were being used for
the primary server, but sessions are not being shared?
Server 1 fails, client moved to Server 2 (backup with no cookies), logs
in. Server 1 comes back up, haproxy detects the cookie from the
original request, directs the client back to Server 1 which doesn't have
access to session data on Server 2.
On Tue, Mar 26, 2013 at 10:43 AM, Chris Sarginson <ch...@sargy.co.uk> wrote:
You would probably need to look at something like this:
http://technet.microsoft.com/en-us/library/cc753897(v=ws.10).aspx
Storing sessions from IIS in an SQL db will allow them to be accessible from
any of your servers.
Chris
On 26/03/2013 09:16, Christophe Rahier wrote:
Hi,
I try to be clear with my question :-)
Our haproxy is in front of 3 IIS web servers.
When a server is down, haproxy doesn't send any traffic to this server, it's
ok. Users needs to log again in our application.
When this server comes alive, users who previously logged (via this server)
need to log again in our application as if haproxy closed their current
session and wants to reconnect them to this server.
How can I avoid this?
Thanks for your help.
Regards,
Christophe
