Bug ID 654003: Portal Access incorrectly prefers charset from meta tag over the value from header

Last Modified: Apr 19, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP APM(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, 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: Mar 28, 2017
Severity: 3-Major
Related AskF5 Article:
K03540372

Symptoms

If charset values in <meta> tag and Content-Type header are not equal, Portal Access prefers value from <meta> tag.

Impact

This may result in unnecessary charset conversion of page content and corruption of some characters. Some characters in rewritten page may be garbled.

Conditions

This occurs if you have charset values in both the <meta> tag and in the HTTP header.

Workaround

Remove <meta> tag from affected pages with iRule or modify its value to contain correct charset.

Fix Information

Now, in Portal Access charset detection, the value from Content-Type header has precedence over value from <meta> tag.

Behavior Change