Forum Discussion
F5 VIP with path in url?
Looking at the requirement given, you need to create a VIP and map backend pool to it as mentioned by PSFletchTheTek . Whatever is present on backend_pool_member/services , same will be appear on https://example.com:8443/services i.e. using F5 VIP.
If they want only specific path i.e. /services to be available and rest else should be blocked then it can be manageble on F5 as well as backend app url config. So there's no clarity on it and need to be checked.
With this, you should be good.
I'd just like to mention that if hardening on backend can't be performed for whatever reason (let's say other servers in your network need to access your node on that same socket with other paths), you can also implement an LTM policy on your BIG-IP to check for /services path in the URL and rejecting any other client request.
You do need to assign an http profile to the virtual server (as well as the LTM policy of course) to achieve this. If we're talking about HTTPS traffic, you also need to import certificates on the BIG-IP unit and configure + assign a clientSSL (end eventually serverSSL too) profile/s to that same VS.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com