[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 389
  • Last Modified:

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?

1 Solution
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.
Walter PadrónCommented:
If you are using ASP.net check this article

"HOW TO: Set Up Multi-Server ASP.NET Web Applications and Web Services"

cipAuthor Commented:
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.

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now