Need workaround for 10.x Caching issue with HTTP::uri updates

In troubleshooting this further today with Tech Support (crunch time deadline was coming too close), we isolated the irule on its own with only one virtual server in http only mode and magically the irule worked. We identified that the order that I had multiple irules applied on the virtual server was the issue. I just moved it to the top of the list and issue was resolved.

 

 

The F5 engineer sent me this summary : On way you can think of it is that when multiple iRules are associated to a virtual server and the event priority is the same (default priority is 500 I believe) then the event blocks of the separate irules will be merged into one event block in the order they are attached to the virtual server. Another method by which you might have solved this would have been to give the event block containing the HTTP::uri code a higher priority so it would run before the lower priority event blocks of the same event. Please see: https://devcentral.f5.com/wiki/iRules.priority.ashx.

 

 

Cheers!