Forum Discussion
Hmm, not quite, I think.
Isnt it the client who makes the acctual call to the backend server, y.domain.com?
x.domain.com responds with a 302 to the client with a new location header and the client trying to make a new request to the new location?
In your scenario, x.domain.com makes the acctual request to y.domain.com in the back, right?
But if there is way to accomplish that instead, im in! :) but im not sure how to do that really..
Best regards,
Johan
Hi Johan,
Jup, it works a treat - I've used it myself a few times as well.
Just keep a bit of an eye on the Profile Scope (can be found under the Properties tab of a policy) to ensure that multiple virtual servers can see the same sessions.
Have a look at the link I posted earlier for an example on how to deploy it - it will show you how it works with multple virtual servers.