Forum Discussion
Russell_E_Glaue
Feb 18, 2009Nimbostratus
Actually the second suggestion is probably better as:
event [] [enable|disable|end] | [enable all|disable all]
So when saying something like:
event HTTP_REQUEST end
or
event end all
Would cause the named event, or all events, to end immediately.
This would also mean that if you want to stop iRule processing, you have to add in the return command so you exit out of the current iRule.
Also, I like your suggestion, skipping ahead to a different priority level.
That is like a 'goto' command.
I have read how from one iRule we can cause the execution of another iRule.
That seems like a possibility to solve this issue, however, I hate the idea of chaining (stacked) iRules together from inside the code.
-RG