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

It's a matter of "state". So a timeline of events might look like this:

 

  1. Client makes a new request to /nice/main1

     

  2. iRule redirects the user to /v

     

  3. Client makes a new request to /v and both parties are completely oblivious to the previous request. This is really the important part. You could technically set a cookie within the redirect to /v from the first request to /nice, but otherwise the new request to /v is a completely separate and new request with no knowledge of the previous request.

     

Any URI evaluation that takes requests to a pool must then be based on the final URI (ie. /v).