Forum Discussion
shadow82
Cirrus
CirrusF5 VIP with path in url?
I've been asked to make a new VIP https://example.com:8443/services How should I apporach this? Do https VIP on port 8443 and ask backend server guys to serve the path part "/services", or...? I'...
Hi,
Do you have any current configuration or are you starting from scratch?
For example, i would expect a virtual server setup on port 8443.
Connected to a back end pool on port 8443 or equivlant.
Is this already in place?
Or i suppose a different question, could you explain your user case / expected result a little more please?
shadow82Cirrus
CirrusIt's totally new VIP that I've been asked to make.
I'm not sure is it some lack of communication within the team that they ask for something like this (url with path) or maybe just full need
- https VIP listening on port 8443
- the first backend service will be "/services"
But should I? Could I prepare the "/services" part on my VIP?
When creating one, it's not possible to provide paths in URL...
For my understanding what services under what directories - it's the backend server job, not F5, right?
hi shadow82,
So, don't get hooked up on the /services thing. As Mayur_Sutare suggests if your external client users that URI it will be passed through straight through to the back end pool member. Also as Mayur_Sutare suggests, other clever stuff can be done if you want to block the root path or other paths IE / or /folder1 etc etc but thats extra config. (Still simple and quick to achieve on the f5!)
So i'd just setup the virtual server on the 8443 port as you identied and the pool and see if it works for them.
In the first instance as its https, i'd leave the ssl client / ssl server config off for now so it acts just as a passthrough with a SNAT and see if this works for you.