Login Page Fails To Render On SSL Terminated Application Tiers
Last updated on AUGUST 08, 2016
Applies to:Oracle Applications Technology Stack - Version 12.0 to 12.1.3 [Release 12.0 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 03-April-2013***
You may have upgraded from 11i to 12.0.X or 12.1.X or you may have implemented SSL termination / acceleration on an existing 12.0.X or 12.1.X environment. You may or may not be running a DMZ setup as per <Note 380490.1>
In simple terms SSL termination is the process of terminating SSL on another device that sits in front of your applications tier. This could be a reverse proxy or perhaps a load balancer. In any case, the client's browser communicates with the external device using HTTPS (SSL) and then the device communicates to the applications tier (external or internal) using HTTP (NON-SSL). The applications tier runs in NON-SSL mode.
When experiencing the issue you may notice that attempts to access the login page https://server.domain:port/OA_HTML/AppsLogin render a blank page.
Also you may experience problems with the logout link as described in <Note 1283920.1>, or problems with diagnostics as seen in <Note 752807.1>
You may notice the following entry in your apache error.log
[warn] Init: (server.domain:443) You configured HTTP(80) on the standard HTTPS(443) port!
or you may see similar errors to that discussed in <Note 732679.1> i.e.
Invalid method in request \x80L\x01\x03
You may have upgraded from 11i to 12.0.X or 12.1.X or you may have implemented SSL termination / acceleration on an existing 12.0.X or 12.1.X environment.
You may or may not be running a DMZ setup as per <Note 380490.1>
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