When configuring an Integration Object where the content type of the HTTP request is specified in the body, testing the request returns an "HTTP/1.1 415 Unsupported Media Type" error as depicted below:
When the content type of the HTTP request is solely specified in the request body, by default, Appian appends charset=UTF-8 to the selected content type. While this is the intended behavior, certain systems will reject requests where the body is UTF-8 encoded.
A workaround for this issue was implemented via AN-107124 in Appian 18.1 Hotfix Package D.
This article applies to Appian 18.1 and later.
Last Reviewed: November 2018
© 2020 Appian. All rights reserved.