Link to home
Start Free TrialLog in
Avatar of cip
cip

asked on

Microsoft Network Load Balacing: single affinity across SSL and HTTP ports

The login page of my web application is under SSL. As soon as a user has logged on, I don't need SSL any more and I redirect him/her to a non-SSL page.

However, it seems that nlb doesn't handle single affinity across different ports. So my user logs in on a server under SSL on port 443, but then gets redirected to another server when it switches to non-SSL on port 80.

This way my Session variables are lost.

Is there a way to handle affinity across SSL and HTTP, or I have to rewrite
the login procedure avoiding the user of Session variables?

Avatar of cj_1969
cj_1969
Flag of United States of America image

You are correct ... session variables are server specific, at least with IIS.
I don't know if you can handle this with a cookie or not since you are changing servers.  You might need to pass the authentication paramter to the new server to set a cookie or sessions variable once redirected.
ASKER CERTIFIED SOLUTION
Avatar of Walter Padrón
Walter Padrón
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of cip
cip

ASKER

I knew that using asp.net i can hold my session variables in a process shared among different servers or in sql server. I was hoping for a faster way to configure the network load balacing cluster but unfortunately it seems that it's not possible.

Thanks for your help.