Forum Discussion
4 Replies
Sort By
- ekaleidoCirrus
Do you need users to see the /example/ or is that just where you want it to land on the server side?
- Vijay_ECirrus
This will change the URI and send it to server:
when HTTP_REQUEST { if { [HTTP::uri] eq "/TestProcess.php" } { HTTP::uri /example[HTTP::uri] } }
This will send a redirect to the client asking them to request the resource again:
when HTTP_REQUEST { if { [HTTP::uri] eq "/TestProcess.php" } { HTTP::respond 301 Location "http://[HTTP::host]example[HTTP::uri]" } }
- dwhite12_255934Nimbostratus
This is just for a backwards compatibility issue, so I believe it's not important for the users to see the actual redirected URI, just where they land. Hope that makes sense.
- ekaleidoCirrus
You should check out ProxyPass. It's an iRule that will handle what you're describing. It essentially shows one URI on the client side and another on the server side. It is well documented as well, so you shouldn't have any trouble standing it up.
https://devcentral.f5.com/codeshare/proxypass-v10-v11