We are in a load balanced environment, the load balancer is www.domain.com, and we have 4 servers that are load balanced using SQLServer sessions for .NET ... www1, www2, etc.
The problem is that we also have some legacy ASP elements that we need to keep working when we disable Sticky IPs on the load balancer. Thus, our idea was in those few places where ASP was necessary, we would bind the user to a specific server, which was decided upon login.
For instance.
1) The user registers on the .NET site
2) The .NET site finds out which server processed the login request and wrote ASP authentication to this server.
3) The server name is stored in the variable
4) Each time the user accesses ASP, we use the server name variable to make sure that he / she gets to the server that has its authentication and session.
The problem is that since the actual login request is just a load balancer, the session does not exist when we direct the user to www3.domain.com/blah.asp because it is a different domain than www.domain.com.
So, I think we are looking at some way to exchange sessions across domains, but with a little twist, I think.
Any help is appreciated, and I hope I have clearly stated the problem.