Problem: IE Browser Cannot Display Page after SSL Certificate is Configured in Web Cache [ID 739725.1]

marlinlineInternet and Web Development

Oct 31, 2013 (3 years and 9 months ago)

82 views


Problem: IE Browser Cannot Display Page after SSL Certificate is Configured in Web Cache
[ID 739725.1]


Applies to:

Oracle Application Server 10g Enterprise Edition
-

Version: 10.1.2.0.0 to

10.1.2.3.0

Web Cache
-

Version: 10.1.2.0.0 to 10.1.2.3.0

This prob
lem can occur on any platform.


Symptoms
:
Oracle Wallet Manager has been used to store a new certificate obtained

from a
Certification Authority. After configuring Oracle Web Cache to use

this new Wallet, accessing the
site with HTTPS is failing with the

f
ollowing error in Internet Explorer:



Page Cannot be Displayed


This problem does not occur in other browsers such as Firefox, Opera, or

Mozilla. It only happens
when Internet Explorer is used.


Cause
:
There is a communication problem between Internet
Explorer browsers and

Oracle Web
Cache. However, the problem is also attributed to the networking

layer installed with the Oracle
Application Server 10g Release 2 (10.1.2) .


Solution
:
In order to fix this issue, the Oracle Application Server 10g Patchset
2

(10.1.2.2) or
Patchset 3 (10.1.2.3) must be applied to pick up the Oracle

Web Cache update. The separate
10.1.0.5 networking codeline installed

would need an update provided in the form of a one
-
off
patch. If these

fixes are not installed together, th
en Internet Explorer 6.0 will not be

able to access
Oracle Web Cache with SSL.


Probleem: De hele certificate chain is in de wallet gezet, maar daarna werkt het nog niet
goed.


De oplossing:

Na het doorgeven van de laatste bevindingen mbt de certificaten,

gaf Oracle de tip door dat de
wijziging nog in een andere file moest worden opgenomen. Dit gebeurt niet automatisch bij het
aanbrengen van de wallet
-
wijziging in de Enterprise Manager.


Behalve het wijzigen van de wallet in zowel de infra als apps server,

moest het ook nog aangepast
worden in de Apps instance


$ORACLE_HOME/Apache/Apache/conf/mod_proxy.conf


Na het herstarten van beide httpd
-
servers bleek het proxy probleem opgelost.