Forum Discussion
"event disable all" does not stop further ltm rule processing
Hello,
"event disable all" stop the current iRule processing and all subsequent iRules from processing as well. You can use just "return", it Causes immediate exit from the currently executing event... So I advise you to use "return" in your case instead "event disable all". Then disable only other subsequent event if needed...
You have to let process this irule
if { not [class match [IP::client_addr] equals my-net-CLASS ] } {
log local0. "===== D R O P P E D : ====================="
log local0.debug "IP::client_addr: [IP::client_addr]"
HTTP::respond 403 content {403 Forbidden}
event disable all
}
For this modify "event disable all" by "return". I think if you use "event disable all" in this case you will have multiple redirect: First
HTTP::respond 403 content {403 Forbidden}
Then server response because you disable event process... this as to impact HTTP::respond.
Let me now if i can help you. regards
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com