OAG Crashes When GET Request Is Sent With Non Zero Content-length Header
(Doc ID 1961865.1)
Last updated on FEBRUARY 18, 2019
Applies to:Oracle API Gateway - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Whenever trying to access a REST request through an OAG Gateway using GET by adding a Content-Type header and using the OAG Policy Connection to connect to a back end system, the Gateway will not respond.
When then trying to access the monitoring trace for above failed response on OAG Monitoring web console, the respective Gateway server will go down.
Using the Connection to URL filter instead of the Connection filter works fine and does not cause the above crash. However, there will be a delay in the API response by the time which is set in the Active time configuration in the HTTP Listener for this API service. This is happening because the Connect to URL is waiting for the content (even if the method is GET) for this duration before it is redirecting to back end system.
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