Enabling ASM in LTM policies causes policy and irule events to be evaluated twice
We are using LTM policies to route traffic to the correct pool based on the Host: header and URL in the request. The policy action also modifies headers in the request, including the Host: header itself, and assigns an ASM policy to the request.
The assignment of ASM policy appear to trigger a second evaluation of the LTM policy, as the matching of the Host: header must include the new value assigned to the request for the ASM policy assignment to take place. This appear to also trigger (at least) the HTTP_REQUEST iRule event to be fired twice.
Apart from the vaste of cpu cycles that must be the result of the duplicated evaluation, it is annoying that the effects taken by the LTM policy and iRule are duplicated. We use the iRule to log the request, and are seeing a lot of duplicated log entries.
Is this a known issue? The system is running version 12.1.2 HF2. The virtual server also have an APM profile attached, and the standard oneconnect profile, although I don't know if that matters.