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?