Getting Started with iRules: Events & Priorities

As this series steams on we go deeper and deeper into what actually drives iRules as a technology. So far we have covered very basic concepts, from core programming ideas and F5 basic terminology thr...
Updated Oct 02, 2023
Version 3.0
200
devops
iRules
series-irules-getting-started
JRahm's avatar
Icon for Admin rankAdmin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.
View Profile
JRahm's avatar
Icon for Admin rankAdmin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.
View Profile
JRahm's avatar
JRahm
Icon for Admin rankAdmin
Dec 14, 2017

@jross, I'd log in each event to be sure, but since the XML would be the HTTP payload, IF you are collecting http payload, I would like HTTP_REQUEST_DATA would fire first, then the xml event immediately after you released it. But if you aren't doing an HTTP::collect, HTTP_REQUEST_DATA won't fire at all, and the xml event would fire after HTTP_REQUEST.