Forum Discussion
ACCESS::policy result in APM/LTM 11.4
I am not sure why this worked in 11.3, but by default HTTP_REQUEST does NOT trigger on the requests that go to the Access Policy engine As such, the very first request that comes in(unauthenticated, presumably), will properly return status of "not_started". What exactly are you trying to do? If you provide a bit more detail, we can certainly try to help steer you towards the proper implementation.
If you truly wanted to interfer with logic within Access Policy execution, then you'd need to enter this event:
when CLIENT_ACCEPTED { ACCESS::restrict_irule_events disable }
This will allow HTTP_REQUEST even to fire on all requests - even during Access Policy execution.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* 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
