OSB Fails when Inbound HTTPS Call is Routed as HTTP Call
(Doc ID 1092053.1)
Last updated on DECEMBER 15, 2023
Applies to:
Oracle Service Bus - Version 10.3.1 and laterInformation in this document applies to any platform.
Symptoms
You have Oracle HTTP Server (OHS) and Oracle service Bus (OSB) 10.3.1 configured. In OSB 10.3.1 you have an HTTP proxy and you would like to implement the following scenario:
client ------https---->OHS----http--->OSB
When the client submits a request to access the proxy WSDL using the above configuration, the following error is returned.
"Error 500--Internal Server Error
Cannot process inbound request to endpoint ProxyService default/Checking the Behavior. over https"
The OSB log will carry the below error message.
Available workarounds:
---------------------
Configure the proxy service with the HTTPS transport. Even though the message comes over the non-SSL port from the Web server, OSB recognizes that the message originally used the HTTPS protocol and accepts the message as an HTTPS message. The SSL port in the OSB domain must be enabled to do this, even though it is not used in this scenario.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |