I have several clients that will connect to an LTM VS on a particular tcp port. Each client will have a URL with a specific port, but no additional URI info. For instance:
Client A - https://www.abc.com:1111
Client B - https://www.abc.com:2222
Client C - https://www.abc.com:3333
We wish to use the same Pool for each of the different Virtual Servers.
10.77.185.10:80
10.77.185.11:80
10.77.185.12:80
When an HTTP request for a generic URL hits the LTM, I want to pass this on to my pool members with an additional context to reflect each customer’s root directory. For instance, an HTTP request to
http://www.abc.com:1111/blah\_blah\_blah\_blah should go to a pool member as /client_a/blah_blah_blah_blah
http://www.abc.com:2222/blah\_blah\_blah\_blah should go to a pool member as /client_b/blah_blah_blah_blah
http://www.abc.com:3333/blah\_blah\_blah\_blah should go to a pool member as /client_c/blah_blah_blah_blah
Is this something that the client should “see”, meaning should their browser reflect the full new URL like http://www.abc.com:1111/client\_a/blah\_blah\_blah\_blah ? Is it even possible to hide this information from the client using the Stream functionality ? If so, should it be a Stream iRule or Stream Profile given the fact that I am looking at HTTP Request headers only and require an HTTP profile associated with my Virtual Servers (404 Page not found | BIG-IP Documentation).