IV87787: INTEGRATION OBJECT HTTP POST WITH XML: CAN'T SEND DOUBLE-BYTE CHARACTERS
Direct links to fixes
Closed as fixed if next.
TRIRIGA Integration Object's xml Post Type requests are not correctly encoding UTF-8 characters. As a result, double-byte characters, although they appear correctly in the server.log when the Integration Object's 'Debug' is clicked, are seen by the receiver as '??.' The problem does not happen if JSON is used.
Use JSON instead of XML
The issue was that post type xml requests were not correctly handling UTF-8 characters. The fix is to include UTF-8 content binding when the entity is being added to the request.
Resolved an Integration Object Http Post scheme issue, where mult-byte characters were not being correctly handled in the outgoing HttpRequest. Please note with this fix, if for some reason your Integration Object Http Post scheme configuration leaves the Content-Type field blank, and the Content-Type is not defined in the Headers field, then the Content-type of the HttpRequest will default to: Content-Type: text/plain; charset=UTF-8. On prior releases it defaulted to Content-Type: null. This is targeted to the 2H2016 release.
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:
Applicable component levels