iRule to have different client-side URIs use different server side tcp ports

Hi Mayur. This sounds like exactly what I want but the LTM policy doesn't seem to work. I built it out like you described but when I try the page in chrome I just get "This site can't be reached", "The connection was reset." IE gives the good old "Can't reach this page." I can see that it's hitting the F5 VIP in the stats but it's not actually maintaining an active connection.

When I first applied the policy above, the F5 forced me to set the HTTP profile to an explicit HTTP profile, and that profile had to have a "DNS Resolver" specified, which I just created. I'm not fully clear on what that's for.

Note that I'm terminating the VS itself on 443 and it should be presenting one of our certs. When playing around with a slew of iRules last week I actually got it to the point where it actually seemed like the connection was going through to the server but the content of the page was severely messed up.

I tried the iRule you have above and again, it seems to get through to the server but I get a runtime error this time which looks like its from the webserver. I think it's because the web server is actually trying to redirect and switch up the URI upon first connection. I'm going to dig in with the web developer some on this part.

If you have any further suggestions on getting the policies to work, I'd love to make that function. Seems the cleanest to understand.