Last Modified: Aug 26, 2020
See more info
Known Affected Versions:
13.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 13.1.1, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 13.1.3, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 15.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168
Opened: Jul 26, 2019
APM Portal Access resource URI might not be re-written for some scenarios involving APM per-request policy.
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.
Two connections from same client IP are executing simultaneously in APM per-request policy subroutine and trying to access APM portal access resource.
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.