NimbostratusHere is the irule, require to just setup any http request get the maintenance massage:
when HTTP_REQUEST {
HTTP::respond 403 content {
This website is currently under scheduled maintenance until 8AM CST on 1/19/2013.
}
}
AltostratusAny combination of multiple HTTP::redirect/HTTP::respond commands will result in the error "Multiple redirect/respond invocations not allowed". Check all iRules that are assigned to a VIP, as a combination across iRules will also result in the error.
Also, check your logic. If a request meets multiple criteria (including across iRules) and multiple matched criteria result in either HTTP::redirect/HTTP::respond you'll encounter the error.
To prevent this you can use a semaphore on the logic statements.
CirrusThe "event HTTP_REQUEST disable" command needs to be in the irule that has the higher priority (or the iRule that is listed first if there are no priorities assigned).
Your log message suggests that the second iRule is still firing. Or at least I am guessing that it is the second iRule based on the name "test_HTTP_to_HTTPS".
Joe