Forum Discussion
Rein_Tollevik
Nimbostratus
Apr 04, 2018Enabling 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 its...
Stanislas_Piro2
Cumulonimbus
Apr 04, 2018I guess the issue is caused by APM and not ASM with LTM Policies.
Did you configure APM with clientless mode?
when working with clientless mode, first packet matches LTM policies, then HTTP_REQUEST, then ACCESS_SESSION_STARTED. when session is allowed, the request is retried (like HTTP::retry), so it evaluate again LTM policies, then HTTP_REQUEST
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects