Forum Discussion
APM Clientless Mode
Clientless-mode removes the 302 redirect pattern from the access policy creation and evaluation process. So instead of getting the APM session cookie in that initial 302 redirect to /my.policy, you get it on the first response from the server. Any subsequent requests from the client, assuming the client sends back the session cookie, will use the same session. If the client does not send back the session cookie, then a new APM session is created for each request. The existing sessions will be removed based on the timeout settings in the access policy.
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