Last updated on FEBRUARY 10, 2016
Applies to:Oracle API Gateway - Version 11.1.2 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 URL Policy instead of Connection Policy 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 Connection URL is waiting for the content (even if the method is GET) for this duration before it is redirecting to back end system.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms