Rule within a Rule on Version 10.2 of BigIP

Understand that multiple iRules assigned to a VIP will essentially "compile together", meaning that the contents of the HTTP_REQUEST event in one iRule will merge with the contents of the HTTP_REQUEST in the other event. This can of course cause problems, so the event priority command can be used to force the event logic to different positions in the merged content. If you simply need to call different iRules based on some condition, you could do VIP targeting and point the traffic flow in the direction of an internal VIP (and its iRule) that then load balances to your application. It isn't a function call in the strictest sense that it returns to where it was called and allows the original rule to continue processing. For that you need sideband calls, procs, or potentially an HTTP::retry mechanism. This method will divert all traffic flow to the internal VIP, which would then process all events south of the event that sent it there.