Forum Discussion
6 Replies
- HamishCirrocumulus
Mmm... Unless the VS you're deploying actually checks the HOST header in the request, it'd never know how many FQDN's your'e deploying behind it. For example if you're tunnelling the SSL through without offload, you'd never know what the user actually wanted to connect to...
It only needs to get more complicated if you require different pools for each FQDN. In which case HTML classes or an HTML content profile that selects a pool based on the HOST header itself would be required.
Of course, you can go as complex as you like...
H
- HamishCirrocumulus
So you have 3 servers with separate FQDN's you want to deploy behind a single VS?
Sounds like what you're building is almost a reverse proxy (I'm assuming your'e keeping the 3x FQDN names for the single VS? or do you want to build a reverse proxy with 1 FQDN that then hides 3 sites utilising a separate path for each?)
You could look at the link here from the 11.5.1 implementations guide. Which details how to build a reverse proxy.
https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-implementations-11-5-1/23.htmlconceptid
H
- nitassEmployee
do you mean to select pool based on host header?
is it similar to this?
irule to select pool based on fqdn
- siyadh_121603Nimbostratusno..its not selecting pool based on host header.... it is selecting service based on host header.
- nitass_89166Noctilucent
do you mean to select pool based on host header?
is it similar to this?
irule to select pool based on fqdn
- siyadh_121603Nimbostratusno..its not selecting pool based on host header.... it is selecting service based on host header.