iRule Errors when upgrading to v14.1

For us a solution has been to add "elseif" or "return" statements to each iRule that has a issue. So far the change to add the "elseif" between each "if" statement appears to now work properly.

Hopefully if someone else has this same issue when upgrading their F5 to v14.1+ this will help them.

when HTTP_REQUEST {
if {[HTTP::has_responded]} {return}
 Rewrite the User-Agent header value if it's empty
if { [string length [HTTP::header "User-Agent"]] == 0 || not [HTTP::header exists "User-        Agent"] }{

 Replace the User-Agent header with a default value
HTTP::header replace "User-Agent" "Mozilla/4.0 (compatible; No User Agent Provided)"
    }
}
`

or

`when HTTP_REQUEST {
if {[HTTP::has_responded]} {return}
if { [HTTP::uri] equals "/portal/" or  [HTTP::uri] equals "/"} {
if {[HTTP::host] starts_with "URL"}{
    HTTP::redirect "http://www.URL.org/contact-us/contact-us.aspx"}
elseif {[HTTP::host] starts_with "path"}{
    HTTP::redirect "http://www.anotherURL.com/Contact-Us/Contact-Us.aspx"}
elseif {[HTTP::host] starts_with "path1"}{
    HTTP::redirect "http://www.anotherURL.com/applications/path1/contact-us.aspx"}
elseif {[HTTP::host] starts_with "path2"}{
    HTTP::redirect "http://www.anotherURL.com/applications/path2/Contact-us.aspx"}
elseif {[HTTP::host] starts_with "path3"}{
    HTTP::redirect "http://www.anthoerURL.com/applications/path3/contact-us.aspx"}
    }
}

Your first iRule is the

HTTP::header

value

when HTTP_REQUEST {

     Rewrite the User-Agent header value if it's empty
    if {([string length [HTTP::header value "User-Agent"]] == 0) || !([HTTP::header exists "User-Agent"])}{
         Replace the User-Agent header with a default value
        HTTP::header replace "User-Agent" "Mozilla/4.0 (compatible; No User Agent Provided)"
    }
}

With your second iRule looks ok other than the formatting and the perfect use case for using

switch

when HTTP_REQUEST {
    if {([HTTP::uri] eq "/portal/") || ([HTTP::uri] eq "/")} {
        switch -glob [HTTP::host] {
            "URL*" {HTTP::redirect "http://www.URL.org/contact-us/contact-us.aspx"}
            "path1*" {HTTP::redirect "http://www.anotherURL.com/applications/path1/contact-us.aspx"}
            "path2*" {HTTP::redirect "http://www.anotherURL.com/applications/path2/contact-us.aspx"}
            "path3*" {HTTP::redirect "http://www.anotherURL.com/applications/path3/contact-us.aspx"}
            "path*" {HTTP::redirect "http://www.anotherURL.com/Contact-Us/Contact-Us.aspx"}
        }
    }
}

I had a similar issue on 14.1. I've figured out what behaviour has changed and what can be done to work around this.

My virtual server has two iRules, the 1st iRule has some header cleansing logic using "HTTP::header replace" this iRule has higher priority, it runs first. My second irule had some logic that sometimes triggers a HTTP response, similar to what you have above. HTTP::redirect triggers a HTTP response so the issue is probably the same.

It appears that you can no longer modify HTTP request headers if you trigger a response at the F5. You need to rejig your code so that "HTTP::header replace" only occurs after any possible HTTP responses have been triggered (and these should be followed by a "return" to stop processing the request).