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

TNY_122436's avatar
TNY_122436
Icon for Nimbostratus rankNimbostratus
Dec 11, 2013

URL Redirect added to existing rule

How can I add another argument so that we can redirect URL's to execute before the code below? For example, I want to have https://domain1.com/nice/main1 to redirect to https://domain1.com/v. Also to...
Kevin_Stewart's avatar
Kevin_Stewart
Icon for Employee rankEmployee
Dec 11, 2013

First keep in mind that a redirect is a physical thing, where the server sends a 30x response to the client with a Location header and a URL for the client to follow. So the client would go to:

https://domain1.com/nice/main1

Get a redirect response and then go to:

https://domain1.com/v

And that's what would show up in the browser address bar. Also consider that a redirect is a preemptive thing, so a response is issued immediately to the client and no traffic is passed to any pools. That may or may not be what you want. Also, the stateless nature of HTTP means that one client request for "/nice/main1" and another for "/v", even if from the same client, might as well be from different clients on opposite sides of the planet. That's why you need state mechanisms in HTTP, like cookies. So given that your question involves a redirect to "/v" and then an evaluation of a URI that won't be in the new request, you may need to reconsider what you're attempting to do.