Bug ID 431508: Incorrect handling of UNICODE settings

Last Modified: Jul 12, 2023

Affected Product(s):
BIG-IP APM(all modules)

Known Affected Versions:
11.4.0, 11.4.1

Fixed In:

Opened: Sep 23, 2013

Severity: 3-Major

Related Article: K15163


If an HTML document contains a <META> tag that includes the parameter 'charset=unicode', and the server does not set character encoding in 'ContentType' header, then APM enforces UTF-16 encoding for this document which may be wrong.


A UTF-8 HTML page may be shown incorrectly if it has a <META> tag that includes the 'charset=unicode' parameter.


This occurs on an HTML page in UTF-8 encoding with the following tag: <META content="text/html; charset=unicode" http-equiv=Content-Type> Back-end server does not set default document encoding.


There is no workaround.

Fix Information

APM displays UTF-8 HTML pages correctly.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips