Forum Discussion
iaine
Jul 31, 2019Nacreous
Hi Dirk
It's because the ACCESS_POLICY_AGENT_EVENT occurs in a different context. **Taken from the APM Operation Guide** The agent runs in the context of TMM to the renderer rather than client to BIG-IP APM.
This means that the HTTP_REQ variables weren't available by the time you had called them. If you had used them in ACCESS_SESSION_STARTED then you'd probably have been fine. To prove this, log HTTP::URI in HTTP_REQ and ACCESS_POLICY_AGENT_EVENT