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.

iRule Recipe 1: Single URL Explicit Redirect

Series Introduction Let's face it: there aren't many people out there who have extensive experience with Tcl. Since iRules is a Tcl dialect, that means that finding a solid iRules solution can be ...
Updated Jun 06, 2023
Version 2.0
application delivery
BIG-IP
iRules
VernonWells's avatar
Icon for Employee rankEmployee
I am an F5 Solutions Architect for Service Providers in the Americas, focusing on Virtualization, SP protocols (Diameter, GTP, DNS) and programmability. Prior to joining F5, I worked as a Wi-Fi Network Engineer for a large U.S. public University, as an Operations Engineer, a network management Software Engineer, and as a Technical Trainer.
View Profile
VernonWells's avatar
VernonWells
Icon for Employee rankEmployee
Mar 05, 2018

Absolutely. In that case, you could use a 

switch
or a data-group (using 
class
). I'd recommend, however, that you look into using a Local Traffic Policy. A policy is easy to set up and doesn't require any iRules.

Anyhow, a 

switch
based approach might look something like this:

when HTTP_REQUEST {
    switch [string tolower [HTTP::host]] {
        "abc.com" -
        "def.com" {
            switch -glob [HTTP::path] {
                "/first/second" -
                "/first/second/*" {
                    HTTP::respond 301 Location "https://aaa.bbb.com/"
                }
            }
        }
    }
}

This would redirect any request for abc.com or def.com that has a URI Target path starting with /first/second to ";.