Forum Discussion

Nimbostratus

Dec 04, 2024

Retain the URL on Browser

Hello Team, We have a requirement , where we have to retain the URL on the browser as is , However at the backend (pool member) user hits land on the other URL/URI. For example: Actual URL (hit...

application delivery

eagertolearn

Nimbostratus

Dec 05, 2024

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.

Paulius
MVP
Dec 05, 2024
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.
- eagertolearn
  Nimbostratus
  Dec 06, 2024
  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.
  - Paulius
    MVP
    Dec 06, 2024
    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?