Last Modified: Oct 16, 2023
Affected Product(s):
BIG-IP APM
Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 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, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Fixed In:
13.1.0
Opened: Dec 28, 2016 Severity: 3-Major
If a URL contains backslashes in the query and/or in fragment parts, it may not be handled correctly in some cases for Internet Explorer and Chrome.
Query and/or fragment part of this URL may be mangled by replacing backslashes. In the example, the query part may be converted to the following string: ?param=aaa/bbb. This may lead to incorrect behavior of web applications.
- HTML page with dynamically generated URL with backslashes in query and/or fragment parts, for example: http://example.com/some/file.html?param=aaa\bbb. - Internet Explorer or Chrome browser.
Use an iRule to correct query/fragment part string.
Now URLs with backslashes in query and/or fragment parts are handled correctly by Portal Access.