Forum Discussion
Bob_10976
Jun 09, 2011Nimbostratus
Thanks for the explaination.. When I say Not redireting to the pool listed, I mean it is not using the Pool that that is listed, in this case secure2.mydomain.com, when the path is matched. Sorry, redirected was probably not the best term. I should have said not being forwarded to the pool secure2.mydomain.com.
What I'm looking for this rule to do is if I go to https://secure.mydomain.com/mcbob then it uses the secure2.mydomain.com pool, if the path is not /mcbob then use the secure.mydomain.com pool. The McBob website exist on both my W2K3 and my W2K8 servers. The W2K3 server uses secure.mydomain.com Pool and the secure2.mydomain.com pool consist of my W2K8 server. We are starting to move some of our apps from our old W2K3 servers over to our new W2K8 servers but not all of them exist there yet, so as I migrate them, one at a time, I simply want a rule that when the path matches go to the W2K8 server, which is the secure2.mydomain.com pool. All of our secure apps are setup for a URL like: https://secure.mydomain.com/something.
The https://secure2.mydomain.com Domain/URL was created only to be used internally for testing apps from outside our network, end users/customers will not use that URL.
Maybe there is a better way to go about this and I'm over looking it, but this rule seems like my best solution as I migrate apps from one server to another.
Thanks,
Bob