Configuring OAG As HTTP Proxy To a HTTPS Endpoint
(Doc ID 2415129.1)
Last updated on OCTOBER 07, 2022
Applies to:Oracle API Gateway - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Attempting to configure OAG 126.96.36.199 to act as an HTTP proxy. We are attempting to use it to proxy to a backend HTTPS service.
After setting up a policy consisting of a dynamic router and connection, it is rejecting CONNECT attempts.
CONNECT <HOSTNAME>:<PORT> HTTP/1.1
User-Agent: Apache-HttpClient/4.5.5 (Java/1.8.0_171)
the path '<HOSTNAME>:<PORT>' does not match against any of the configured URIs.
recoverable error handling transaction:
HTTP/1.1 404 general exception
Is it possible to setup OAG as an HTTP proxy in this scenario?
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