Bug ID 641307: Response Page contents are corrupted by XML policy import for non-UTF-8 policies

Last Modified: Jun 15, 2024

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

Known Affected Versions:
11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0, 12.1.4.1

Opened: Jan 25, 2017

Severity: 3-Major

Symptoms

If non-UTF-8 policy has Response Pages configured with non-ASCII characters, the Response Page contents will be corrupted by an XML export/import.

Impact

Response Page contents are corrupted

Conditions

1) Response pages are configured with Non-ASCII characters in a non-UTF-8 Policy. 2) The Policy is exported via XML export.

Workaround

1) Use binary policy export/import for non-UTF-8 policies. or 2) Encode the non-ascii characters using the html entities/code representations of them. (Example: ??? -> 日本語)

Fix Information

Response Page contents are correctly exported.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips