This section describes the changes in Oracle HTTP Server documentation.
The List of Included Modules section in Administrator's Guide for Oracle HTTP Server does not include information about the following third-party modules that are also bundled with Oracle HTTP Server by default.
mod_cache.so (Windows only)
mod_disk_cache.so (Windows only)
The Terminating SSL Requests section in Administrator's Guide for Oracle HTTP Server is placed in the wrong section Managing Oracle HTTP Server Logs at present. It should have been in the section Implementing SSL.
In addition, the following step has been added in Terminating SSL Requests, after Step 3: Click Clusters.
Step 4 . Select the cluster to which you want to proxy requests from Oracle HTTP Server.
Log in to the Oracle WebLogic Server Administration Console.
In the Domain Structure pane, expand the Environment node.
Select the cluster to which you want to proxy requests from Oracle HTTP Server.
The Configuration: General tab appears.
Scroll down to the Advanced section, expand it.
Click Lock and Edit.
Set the WebLogic Plug-In Enabled to yes.
Click Save and Activate the Changes.
Restart the servers for the changes to be effective.
The Configuring Plug-In Manually section in Using Oracle WebLogic Server Proxy Plug-Ins specifies an incorrect path for the
mod_wl_ohs.conf file. The
mod_wl_ohs.conf file is actually located in the path:
In the Sample weblogic.conf Configuration Files section in the Using Oracle WebLogic Server Proxy Plug-Ins Guide, the location entries, "Except WebLogicHost,WebLogicPort, WebLogicCluster, and CookieName" are incorrect and must be removed from the following sample codes:
Example Using WebLogic Clusters
Example Using Multiple WebLogic Clusters
Example Without WebLogic Clusters
The Deprecated Directives for Oracle HTTP Server section in Oracle WebLogic Server Proxy Plug-Ins incorrectly mentions that to enable plug-in logs, set
OraLogSeverity to TRACE:32 If
OraLogMode is set to
OraLogSeverity must be set to TRACE:16 instead.