For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Colin_Walker_12's avatar
Colin_Walker_12
Historic F5 Account
Aug 13, 2013

So are you looking to have their entire browsing experience only show website.domain.com/? Meaning you want to remove any URI context that the servers return back each time, so that it isn't visible in the URI? (Note: This is not advised and can lead to some ... interesting issues). If so, then you'll need to add a response section and do some more advanced legwork as well.

 

If all you're trying to do is seamlessly re-write the URI to the new path then you're pretty close. You may want to consider adding a couple more cases such as a blank URI or, as Arie above said, a default document name that also get re-written. The functionality you already have, however, should be pretty much what you need to invisibly re-write website.domain.com/ to website.domain.com/SOME_URI without the client seeing the change.

 

Colin
blwavg_10621's avatar
blwavg_10621
Icon for Nimbostratus rankNimbostratus
Aug 13, 2013
Over IIS, it only shows website.domain.com/ for the client and when I do it over the F5 is shows the full URI. Which is a pretty easy setup in IIS, so why do you think this specifically would cause problems? Something I just noticed that I should add it that this site does add a tag of Home. So the client sees HTTPS://website.company.com/Home. I do not know if that makes a difference. When I use my basic iRule above it does the same thing with the full URI path shown. I also do not know if IIS it taking the URL and rewriting to the be servername.company.com/URI_REWRITE_PATH_HERE.