> in an environment that was not load balanced. In that
> environment, everything related to cflogin worked properly.
>
> Moving the code to a load balanced environment (non-sticky),
> resulted in the breaking of only cflogin. In the LB
> environment, there was no explicit use of sessions and the
> two servers were not replicating session variables.
> Additionally, we could observe the switching of the user
> between machines ( by outputting the current machine name),
> and note the discrepancies occuring at that time.
By default, I suspect that the cookie written by CFLOGIN is host-specific. I
don't know how it works in a load-balanced environment, but I suspect it
doesn't work at all unless you ensure that users are redirected to the same
server which handled their initial request - in other words, "sticky
sessions".
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
