APM HTTP requests logs on backend side

We strongly suggest to avoid new deployments with Portal Access. It was designed to operate with legacy backend web apps that are impossible to publish on a single DNS endpoint, such as when an app contains weird TCP ports, plaintext HTTP, multiple backend servers, and the like. Modern apps are usually all encrypted, and all published on a single DNS endpoint, and can be served using an APM virtual server in "LTM+APM" mode.

Portal Access uses a proxying/rewriting engine to rewrite javascript and HTML in real-time as it transits the box. While it used to be pretty comprehensive, modern web apps, frameworks, and advanced newly-added HTML and Javascript features limit its usefulness.

Info about Web Access Management: https://my.f5.com/manage/s/article/K08200035#link_06

Info about Portal Access:

https://my.f5.com/manage/s/article/K08200035#link_07

Info about how to troubleshoot Portal Access:

https://my.f5.com/manage/s/article/K14184