Oracle API Gateway Removes Content-Transfer-Encoding Header From Request When Gateway Setup As A Service
Last updated on AUGUST 05, 2016
Applies to:Oracle API Gateway - Version 11.1.2 and later
Information in this document applies to any platform.
After installing OAG and setting up the required policy, an issue is encountered as described in:
Oracle API Gateway Removes Content-Transfer-Encoding Header from Request (Doc ID 2114367.1)
The workaround described here is to set the environment variable KEEP_CTE to true in the console window where the Gateway is being started.
However, in this case, the Gateway itself is not being started at the command line. It has been installed as a service and is being started differently. To start a service, the command
service vshell-Group1-Gateway1 start
is issued. When using this approach, setting the environment variable in the console window before startup does not overcome the problem.
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