On 3/22/06, wolf2k5 <[EMAIL PROTECTED]> wrote: > To reply to my own question: it looks like that the cflogin cookie > includes the username/password info (I think it's base64 encoded), > when jumping from one server to another, the user is already logged > into the second server.
I take this back: I did better testing and the user is NOT automatically logged into the second server. Basically there is a cflogin limitation with simple DNS round robin load balancing (no clustering) on multiple web servers: the login session isn't shared between the multiple web servers (even if the cflogin cookie contains the full username/password info, that would be sufficient to automatically re-authenticate the user behind the scenes on another server), apparently, besides the cflogin cookie on the client, each CF server maintains its own internal state of the logins/logouts sessions. What would be the better/easiest way of managing a logins on a load balanced application w/o clustering the CF instances? I used the session word to mean login sessions, not CF session variables. Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:236025 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
