Bug ID 756213: No support of injection into XHTML pages

Last Modified: Jul 03, 2019

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6

Fixed In:
15.0.0

Opened: Jan 22, 2019
Severity: 3-Major

Symptoms

FPS does not inject the JS engine into pages with 'application/xhtml+xml' content-type.

Impact

DataSafe features (e.g., encryption and obfuscation) are not working on XHTML pages.

Conditions

The content-type of the response is 'application/xhtml+xml'.

Workaround

None.

Fix Information

FPS now injects JS engine into 'application/xhtml+xml' pages. Note: JS removal detection does not work in this case (but it does work for HTML pages).

Behavior Change