F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

Zev's avatar
Zev
Icon for Altostratus rankAltostratus
Mar 16, 2020

iRules fail in v14.1.2.3

I recently upgraded from v12.x to v14.1.2.3 and simple redirect/rewrite iRules seem to fail. At first I removed the iRule, deleted it and just recreated it and this worked for a bit (2nd rule below)...
cloud
iRules
LTM
redirects
v14.1.2.3
Zev's avatar
Zev
Icon for Altostratus rankAltostratus
Mar 17, 2020

SB,

 

Thanks, this is the most direct answer I have found. I am not exactly sure how I would integrate HTTP::has_responded in to this 2nd iRule as I need the rewrites to function/take precedence. It seems the order is different as well. I was just beginning to understand iRules in v12 now I am a little lost again.

Simon_Blakely's avatar
Simon_Blakely
Icon for Employee rankEmployee
Mar 17, 2020

First - always use priority statements to control event execution order if you are using multiple irules with the same event.

 

Second, at the start of the earliest executing event, set variables that contain the things you might need in later irule events (HTTP::host, HTTP::uri, HTTP::path, etc). Then refer to the variables rather than the HTTP:: functions.

 

Use the following code fragment after a HTTP::redirect/HTTP::respond

   ...
    HTTP::redirect "<location>"
    event disable
    return
    ...