Multiple context paths on same FQDN and real servers
Hi,
We are currently in the process of migrating services from Cisco ACE 4710 to F5 BIG IP appliances.
Could you please advise if there is any way to configure on F5s, under the same virtual IP/FQDN, something similar to the following:
Service A: http://foo.domain.int/servA >>> redirecting to HTTPS https://foo.domain.int/servA >>> SSL termination >>> real servers: 10.10.10.10:80 , 10.10.10.11:80 and health monitor target: /servA/monitoring
Service B: http://foo.domain.int/servB >>> redirecting to HTTPS https://foo.domain.int/servB >>> SSL termination >>> real servers: 10.10.10.10:80 , 10.10.10.11:80 and health monitor target: /servB/monitoring
Service C: http://foo.domain.int/servB >>> redirecting to HTTPS https://foo.domain.int/servB >>> SSL termination >>> real servers: 10.10.10.12:80 , 10.10.10.13:80 and health monitor target: /servB/monitoring
Notes: The FQDN (and the VIP address) should be the same for services A, B and C. The real servers will be accessible via SNAT (i.e. F5 operating in one-armed mode). The real servers 10.10.10.10:80 and 10.10.10.11:80 should be the same for both services A and B. If the health monitor target of any of the three services fails (e.g. service A) then the F5 to respond with a maintenance message when end-users target the URL of the failed service (e.g. http://foo.domain.int/servA) while the other two services remain functional.
Thanks,