pool down redirect problem

Ok thanks. I think I understand. It flows through and finds the /maintenance and applies that as the response, then it hits the pool_down and also tries to apply that as a response. Is that right?

I ended up making three irules. The first one isn't attached to anything it just initializes the global variables. The second one checks for the uri of /maintenance and then calls an "event disable all". The third one then corrects certificate errors and status of the pool. Is this a proper way to do it?

...iRule number one (not assigned)

when RULE_INIT {

set ::wwwqawait 10

set ::wwwqaprot "https://"

set ::wwwqahost "www.site.com"

set ::wwwqafail "/maintenance"

set ::wwwqapool "Test_POOL"

}

...iRule number two

when HTTP_REQUEST {

check to see if the URI of the request starts with /maintenance

if { [string tolower [HTTP::uri]] starts_with "$::wwwqafail" }

{

HTTP::respond 200 content blah-server-down

...redirects to wwwqahost in wwqawait seconds...

event disable all

}

...iRule number three

when HTTP_REQUEST {

check to make sure connection is secure

if { [TCP::local_port] != 443 }

{

HTTP::redirect $::wwwqaprot[HTTP::host][HTTP::uri]

}

make sure a short host (2-part) is a correct match for our certificate (3-part)

if { [string length [getfield [HTTP::host] "." 3]] == 0}

{

HTTP::redirect $::wwwqaprot$::wwwqahost[HTTP::uri]

}

make sure a long host is a correct match for our certificate

if { [string length [getfield [HTTP::host] "." 4]] > 0}

{

HTTP::redirect $::wwwqaprot[domain [HTTP::host] 3][HTTP::uri]

}

check to see if the pool is down. if so, redirect to the maintenance page

if { [active_members $::wwwqapool] < 1 }

{

HTTP::redirect $::wwwqaprot$::wwwqahost$::wwwqafail

}

end http request block

}

when HTTP_RESPONSE {

HTTP::header remove Server

}

 without event disable

[root@ve10:Active] config  b virtual bar list
virtual bar {
   snat automap
   pool foo
   destination 172.28.19.79:80
   ip protocol 6
   rules {
      rule1
      rule2
   }
   profiles {
      http {}
      tcp {}
   }
}
[root@ve10:Active] config  b rule rule1 list
rule rule1 {
   when HTTP_REQUEST priority 10 {
   log local0. [HTTP::uri]
}
}
[root@ve10:Active] config  b rule rule2 list
rule rule2 {
   when HTTP_REQUEST priority 20 {
   log local0. [HTTP::uri]
}
}

[root@ve10:Active] config  tail -f /var/log/ltm
Dec  5 00:59:16 local/tmm info tmm[7926]: Rule rule1 : /
Dec  5 00:59:16 local/tmm info tmm[7926]: Rule rule2 : /
Dec  5 00:59:16 local/tmm info tmm[7926]: Rule rule1 : /f5.gif
Dec  5 00:59:16 local/tmm info tmm[7926]: Rule rule2 : /f5.gif

 with event disable

[root@ve10:Active] config  b rule rule1 list
rule rule1 {
   when HTTP_REQUEST priority 10 {
   log local0. [HTTP::uri]
   event disable all
}
}
[root@ve10:Active] config  b rule rule2 list
rule rule2 {
   when HTTP_REQUEST priority 20 {
   log local0. [HTTP::uri]
}
}

[root@ve10:Active] config  tail -f /var/log/ltm
Dec  5 01:00:42 local/tmm info tmm[7926]: Rule rule1 : /

I am sure you are correct, but the way I am sequencing the rules *seems* to make it work.

I saw those references with and wthout the :: prefixes and also the static declaration. Unfortunately I am a lowly application developer and do not know what version of F5 we are on. Nobody here knows how to write irules so I had to learn recently. If we are on the right version should I change to static?

Also, I discovered on the dashboard that the F5 is on Version 10.2.2 (Build 930). So, that being the case, I should change my init variables to static and I *do not* have to prefix them with :: correct?