For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

wlepkin_98758's avatar
wlepkin_98758
Icon for Nimbostratus rankNimbostratus
Jun 06, 2014

Order of XML_CONTENT_BASED_ROUTING execution

Hi, I've seen all the nice charts showing the order of http event execution, but can't find anything showing how that might relate to XML_CONTENT_BASED_ROUTING event execution.   I have an HTTP_RE...
application delivery
devops
iRules
LTM
wlepkin_98758's avatar
wlepkin_98758
Icon for Nimbostratus rankNimbostratus
Jun 09, 2014

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_Bene1's avatar
    What_Lies_Bene1
    Icon for Cirrostratus rankCirrostratus
    Jun 10, 2014
    Ahh 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_98758's avatar
    wlepkin_98758
    Icon for Nimbostratus rankNimbostratus
    Jun 10, 2014
    I'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.