iRule - unexpected behavior
Hello Community, I have recently experienced an unexpected behavior from an iRule, where the http responses were intermittent and failure detected on the last event in the iRule HTTP_RESPONSE_RELEASE. We have noticed the odd behaviour started when the log destination pool members failed to respond to health-check monitor (server down). Below is a snippt of the iRule event where the failure observed. when HTTP_RESPONSE_RELEASE { # figure out the final duration and add it to the IPFIX log set stop [expr {[clock click -milliseconds] - $start}] IPFIX::msg set $rule1_msg1 flowDurationMilliseconds $stop # send the IPFIX log IPFIX::destination send $static::http_rule1_dest $rule1_msg1 } I'm questioning two things: Why the failure was intermittent and havent affeted all responses? Why the pool memebrs status affected the iRule when they went down? I'd appreciate any explanation. Regards, Sarah.
What's the purpose of the catch block in an ASM_REQUEST_BLOCKING scenario
We're returning custom ASM-error pages by using an irule whose initial structure follows the principle of the article ASM_REQUEST_BLOCKING. Some month ago i decided to remove the last block 'when HTTP_RESPONSE_RELEASE'. Today i temporarily re-added it and was quite surprised about the log entries. Although the irule works as expected, the content of the catch block is getting executed. How do i identify the typ of the exception thrown by the irule? And what action should it take in this case, since everything works fine?