502 Bad Gateway Error Thrown When Trying to Configure Reverse Proxy to SSL Resource While Retaining the Initial Access URL
Last updated on MARCH 03, 2017
Applies to:Oracle HTTP Server - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
When trying to access a resource on non-ssl port of the OHS which internally redirects to an SSL enabled backend server (retaining the initial non-ssl URL in the browser) , a 502 Bad Gateway Error is thrown.
The ohs1.log has the below entries during this time
In the above configuration, http://ohshostname:ohsport/newanalytics gets redirected to http://testing1.com/newanalytics without any issue and the URL in the browser remains http://ohshostname:ohsport/newanalytics
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms