E1: AIS Invalid Content-Encoding Header in AIS for formservice Calls is Returning the Header "Content-Encoding: UTF-8" when Using Apache HTTP Connection.
(Doc ID 2288983.1)
Last updated on JULY 26, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.
When running a 3rd party Rest call to the AIS server creating an orchestrator endpoint like /jderest/orchestrator/USER_QUERY, the endpoint tests successfully using the provided /jderest/client/orchestrator.html client and via SOAPUI Tool. However, a third party application that uses Apache HTTP connection, generates "org.apache.http.HttpException: Unsupported Content-Coding: UTF-8" error message. According to Apache: "HTTP protocol specification defines gzip, compress, deflate and identity as valid content coding schemes. One should be using identity instead to signal that no content transformation is expected. This is an invalid Content-Encoding for compression, such as gzip.
Is it possible to configure the REST endpoint to not send the encoding as UTF-8?
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