Charset Content-Type Option not respected when using Multipart/related Message Towards OSB
(Doc ID 1937797.1)
Last updated on OCTOBER 01, 2021
Applies to:
Oracle Service Bus - Version 11.1.1.7.0 and laterInformation in this document applies to any platform.
Symptoms
When invoking Oracle Service Bus (OSB) using a multipart request where the charset is only specified in the part headers, OSB does not parse the request correctly and characters can get scrambled.
The first Content-Type (multipart/related) does not specify a charset, but the Content-Type of the first part does (Content-Type: text/xml; charset=UTF-8).
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |