Load balancing ASP.NET WIndows 2003 while preserving session state.
Posted on 2008-10-22
I have an interesting question.
We recently setup a web farm using 2 web servers and 1 database server on a Zeus shared load balancer using round robin traffic shaping. Our sessions are stored via cookie on the user's local machine. The problem we're running into is, given that the load balancer treats HTTP and HTTPS as separate requests, sometimes a user may start at one machine, and end up at the second machine when they call up an HTTPS page, or vice versa.
I know the best option is to store session data in the database to avoid the issues with HTTP/HTTPS, but are there any other options? For example, would Windows NLB solution be a viable option to preserve session state, or are there other load balancers that can do some form of cookie based load balancing, or..
Essentially, I'm trying to determine if there's an option to properly load balance 2 Windows Server 2003 Standard web servers while avoiding the issues caused with changing servers during HTTP/HTTPS switchovers, etc.
If that makes sense.