Gzip Compression Issue In OAG
(Doc ID 2142881.1)
Last updated on AUGUST 19, 2022
Applies to:Oracle API Gateway - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
In OAG 188.8.131.52, trying to send a request to a web service that only accepts http compression resulted in the response not recognizing the gzip format. Even after configuring a remote host that accepts Content length in request & response and also gzip for the encoding, sending the request will result in the following message.
'Request must be sent using HTTP compresssion"
However, it was discovered that when content-length is enabled through the Remote Host, the gateway does not encode the request which is the expected behavior since the gateway cannot create a request with Content-length and Content-encoding: gzip being enabled. (refer to bug 22324072 for more information). Therefore, the only supported way to send the request is to have the Content-length headers disabled. This is where the current issue comes into play.
Removing the Content-length headers is causing OAG to be non-responsive after a timeout. Then it shutsdown. The following error is seen in the trace:
1. Under Remote Host Settings uncheck boxes for 'Include Content length in request & response' (since gateway does not allow content length and gzip options selected)
2. Under Advanced tab opted gzip for both Input/Output encodings
3. Deployed the changes
4. Submit the Request
5. This causes the OAG to be non-responsive after a timeout and then it shuts down.
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