Bug ID 809629: APM Portal Access resource URI might not be re-written for some scenarios involving APM per-request policy.

Last Modified: Nov 23, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2

Fixed In:
16.0.0

Opened: Jul 26, 2019
Severity: 3-Major

Symptoms

APM Portal Access resource URI might not be re-written for some scenarios involving APM per-request policy.

Impact

The client session that first finishes the APM per-request policy subroutine will be redirected a re-written resource URI for portal access resource. All other sessions that simultaneously entered the subroutine will not be redirected to a re-written resource URI for portal access resource and instead will be redirected to the backend server URI.

Conditions

Two connections from same client IP are executing simultaneously in APM per-request policy subroutine and trying to access APM portal access resource.

Workaround

None.

Fix Information

All client IP based sessions that are simultaneously executing inside the subroutine, will see a re-written URI when trying to access APM portal access resource.

Behavior Change