IT21452: DATAPOWER CANNOT PARSE UTF8 BOM PREFIXED XML IF BOM IS SPLIT ON DIFFERENT TCP PACKETS
Fixes are available
Closed as program error.
In cases where a UTF8 BOM (Byte Order Mark) prefix is split across different TCP packets and DataPower is parsing the input as XML, DataPower will log a parsing error.
If using a Microsoft TLS client, forcing TLS 1.2 can avoid this issue. This can be worked around on DataPower by changing your service configuration to non-xml input, and parsing the input into a buffer using Gatewayscript.
Affected is parsing of UTF8 BOM prefixed XML. In case XML message is split on several TCP packets, and first packet does not contain full UTF8 BOM, DataPower generates a parse error.
Fix is available in 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199 and 188.8.131.52 For a list of the latest fix packs available, please see: http://www-01.ibm.com/support/docview.wss?uid=swg21237631
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels