Forum Discussion
wlepkin_98758
Jun 09, 2014Nimbostratus
Hi, thanks for the response.
It seems that the old post was correct, and HTTP_REQUEST fires first no matter what, at least in LTM 11.4.0, even if the two events are in separate iRules with the XML_CONTENT_BASED_ROUTING iRule first in the order. But HTTP:: commands do work with an XML_CONTENT_BASED_ROUTING event, so I've just incorporated them into that and it's working the way I want.
Thanks again for your help. I guess I could have easily figured this out without posting, but now others know too.
Wayne
- What_Lies_Bene1Jun 10, 2014CirrostratusAhh great. Yes, very worthwhile and now I can update the event order diagrams which will further extend that. Did you work out which fired first?
- wlepkin_98758Jun 10, 2014NimbostratusI've tested with only two events, HTTP_REQUEST and XML_CONTENT_BASED_ROUTING, and I found that no matter what I do HTTP_REQUEST fires first. That is, whether both events are in the same iRule with XML_CONTENT_BASED_ROUTING first, or in separate iRules with the XML_CONTENT_BASED_ROUTING rule first in the order, HTTP_REQUEST still fires first.