Bug ID 848673: Portal Access message event has wrong origin if message originates from split tunneled frame

Last Modified: Oct 06, 2020

Bug Tracker

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

Known Affected Versions:
14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5

Fixed In:
16.0.0

Opened: Nov 11, 2019
Severity: 3-Major

Symptoms

Unexpected exceptions, and other issues can be visible dependent on web-application internal logic.

Impact

Web-application does not operate as expected. Messages sent from the iframe with src=http://twitter.com to the main window with URL http://my.company.com can cause exception when receiving data.

Conditions

Portal Access message hat originates from a split tunneled frame; for example, in a split tunneling configuration: REWRITE *://* BYPASS *://*twitter* *://*twimg*

Workaround

Use a custom iRule to handle this situation.

Fix Information

Portal Access message event now has the correct origin if the message originates from a split tunneled frame.

Behavior Change