Forum Discussion
Retain the URL on Browser
Hi Paulis
Thanks, but it's not working with pool.
Providing more clarity :
1) slight addition in the backend URL
Actual URL (hit by user) - 123.abc.com/test1 , At Backend (pool member) : This hit should forwarded to 123.xyz-ha.com/test1
For end user, URL should not be change and he can only see 123.abc.com/test1 on his browser.
2) addition and changes in URI
Actual URL (hit by user) - 123.abc.com/test1 , At Backend (pool member) - This hit should forwarded or land on 123.xyz-ha.com/hello/check12
For end user, URL should not be change and he can only see 123.abc.com/test1on his browser.
eagertolearn Number 2 contradicts Number 1. What is the reasoning of forwarding to the server on 123.xyz-ha.com/test1 to then just forward it to 123.xyz-ha.com/hello/check12 instead? Can you please provide your virtual server configuration to see if I missed anything because the above iRule should work for the original purpose.
- eagertolearnDec 06, 2024
Nimbostratus
Hi Paulius,
123.xyz-ha.com/hello/check12 is just the backend URL, But application team want to access it using 123.xyz-ha.com/test1 from browser.
- PauliusDec 06, 2024
MVP
eagertolearn why not just map 123.abc.com/test1 to 123.xyz-ha.com/hello/check12 instead since the client isn't suppose to use URL 123.xyz-ha.com/test1?
- zamroni777Dec 08, 2024
MVP
does request to 123.abc.com/test1 hit f5 vserver?
if yes, then Host header rewrite in Paulius answer should work.if not, then you need to ensure that dns resolution of 123.abc.com hits vserver ip address.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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
