Bug ID 673500: Portal Access: support of relative URLs in HTML tags <link rel=import ...>

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 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.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,

Fixed In:

Opened: Jul 11, 2017
Severity: 3-Major


HTML components can be imported into HTML page via <link rel=import ...> tags. If the same HTML component is referenced by several such tags, only the first import is performed. But in the case of Portal Access, the browser cannot recognize identical URLs in some cases due to URL mangling. This may lead to unnecessary multiple loading of the same HTML component.


The component should be loaded once, but Portal Access rewrites both URLs. The browser cannot recognize its identity, so the component is loaded twice, and scripts inside are executed twice. Web application may not work correctly.


-- HTML page with several <link rel=import ...> tags referring to the same HTML component but using different representation of its URL, for example: <link rel=import href=/some/path/component.html> <link rel=import href=../component.html> -- '/some/path' and '../' refer to the same back-end path. -- Chrome browser.



Fix Information

Now Portal Access supports relative URLs in HTML import tags correctly.

Behavior Change