Forum Discussion
QNetOps_179308
Nimbostratus
NimbostratusEnable event Processing after HTTP::respond
I currently have an iRule that responds directly from the F5 with the HTTP::respond event. However, I would also like other iRules which log request/response to fire but they are not. From my searche...
Kevin_Davies_40
Nacreous
NacreousDo it last. All iRules can be associated with a priority in the format
when EVENT priority X {
So iRules of the same EVENT type run in priority sequence from 1 to 1000. The default priority when not specified is 500.
Separate out your HTTP::respond to an iRule with a high priority than the rest so the other iRules run first.
when HTTP_REQUEST priority 900 {
HTTP::respond 200 content $my_data
}
QNetOps_179308I should have been more detailed. Currently our iRule logs during the HTTP_RESPONSE step (so that all the information needed for the logs are available when we are logging a normal response) and the iRule with the HTTP::respond is during the HTTP_REQUEST step. My understanding is that setting the priority wouldn't solve this particular scenario because later steps would never fire.