Charset Content-Type Option not respected when using Multipart/related Message Towards OSB
Last updated on JANUARY 04, 2018
Applies to:Oracle Service Bus - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
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).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms