We're implementing a pair of network load balancers for our externally and internally facing web servers. we do not plan to use session state services on either NLB, and accept that if a node goes down, the user will have to re-authenticate on the new server, and start a new session.
we have an ASP.Net4 application however which redirects to an external service (a payment processor) and then uses a statically configured link to return the user to our externally facing URL.
I have two questions:
When the user returns to the site after performing a payment, is there any way to make sure they connect to the server their session is currently on?
When a user on the Internally facing NLB completes a payment, the service will attempt to return them to the external NLB. is there a way to intercept and redirect them back to the internally facing cluster, and then the server upon which their active session resides?