Oracle® Fusion Middleware

Release Notes for Oracle HTTP Server

12c (12.1.3)

E48287-05

April 2018

This document contains important release information about Oracle HTTP Server 12c (12.1.3).

Oracle Fusion Middleware Release Notes for Oracle HTTP Server, 12c (12.1.3)

E48287-05

Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

Primary Author: Trupthi NT

Contributor: Kevin Clark, Leonard Bottleman, Sriram Natarajan

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Introduction

- Latest Release Information

- Purpose of this Document

- System Requirements and Specifications

- Certification Information

- Product Documentation

- Oracle Support

- Licensing Information

2 What’s New in this Release

- New Features

- New and Changed Features in 12c (12.1.3)

- New Features in 12c (12.1.3)

- Significant Updates in 12c (12.1.3)

- SSL FIPS Mode Can Be Configured as a SSLFIPS Directive

- New and Changed Features in Release 12c (12.1.2)

- New Features in Release 12c (12.1.2)

- Release 12c (12.1.2) Introduces the WebLogic Management Framework

- OHS Release 12c (12.1.2) Supports FIPS 140

- Search Capability on mod_wl_ohs Configuration Page

- AutoFill Capability on mod_wl_ohs Configuration Page

- Significant Updates in Release 12c (12.1.2)

- WLS Plug-in Logs Are Now Part of the Web Server Logs

- sqlnet.ora NZ Trace Logging Mechanism is No Longer Supported

- Privileged Ports on UNIX Have Different Support Implementation

- ECID Information

- Terminate SSL Requests

- Deprecated Features

- Deprecated Features in 12c (12.1.3)

- Modules Deprecated

- Support for SSL Protocol Version 3 Removed

- The shmht value in SSLSessionCache is Deprecated

- Deprecated Features in 12c (12.1.2)

- Integration with Oracle Web Cache

- mod_oradav

- mod_osso

- SSO Plug-ins for Third-party Web Servers

- Oracle WebLogic Server Proxy Plug-Ins for Third-party Web Servers

- SSL Protocol Version 2 and Export Ciphers

3 Known Issues and Workarounds

- Known Issues in Oracle HTTP Server 12c (12.1.3)

- Start and Stop Scripts Require Directory Write Permission

- Oracle HTTP Server Instance Fails To Load mod_cgid

- Continuously Hitting Web Application Through OHS on IBM-AIX Might Generate a Large Error Log

- Configuring Certain Protocols and Ciphers Is Not Allowed

- Starting Node Manager in Collocated Environment Generates System Messages

- Oracle HTTP Server in FMW Control Does Not Recognize Deployer Role

- ServerName Directive Does Not Support IPv6

- Bad CLASSPATH Environment Variable Can Break WLST

- Oracle HTTP Server Configuration Assistant Launcher Fails on Solaris 5.10

- Disable SSL Security Protocols

- Default Value for the MaxPostSize Web Server Plug-in Parameter has Changed

- FIPS is Not Available on the Windows Platform

- Installing Oracle HTTP Server on Oracle Linux 7 Environments

- SSL Certificate Order of Attributes with a DN is Incorrect

- Known Issues in Oracle HTTP Server 12c (12.1.2)

- Using shutdown() Without Parameters Shuts Down WebLogic Server

- Multiple WLST Versions

- No Command to List All OHS Instances, States, and Ports

- Configuration Wizard Does Not Present a Summary Screen

- Standalone Instances Start in UNKNOWN State

- nmServerStatus() Returns UNKNOWN for Non-existent Instances

- No Automatic Port Allocation for Standalone Instances

- nmStart(), nmServerStatus(), and nmKill() Require ServerType Parameter

- Instances Can Be Deleted in the RUNNING State

- Private Keys Should Not be on a DMZ Machine

- Missing Libraries Might Cause HTTPD to Exit Without Notice

- Create DOMAIN_HOME/servers/<instancename>/logs manually when Diagnosing Start-up Failures

- Installer Sporadically Hangs on Specify Security Updates Screen

- Warning Appears if No Oracle HTTP Server Instance is Created

- Backslashes in Paths in ohs.plugins.nodemanager.properties must be Escaped

- Creating Instance Named "adminserver" Throws Exception

- DMS Displays Incorrect Message if OHS is Down

- Node Manager 12c (12.1.2) OHS Throws Java Exception on AIX

- Set PATH Environment Variable Manually if OHS on Windows Fails to Start

- Recovering Instance on Managed Node Requires tar/untar Commands

- OHS Instance Creation with Config Wizard Does Not Require Machine Assignment

- httpd.exe Fails to Start

- SSLWallet Directive in ssl.conf Might be Saved Incorrectly

- CONFIG_FILE_PATH Setting for apxs in a Standalone Domain

- Create Log Directory Manually When Diagnosing Startup Failures

- createOHSTestDomain() Should be Used Only in Offline Mode

- OHS on UNIX Might Not Start When Listening Port is Configured in Reserved Range

- FIPS is Not Available on the Windows Platform

- SSL Certificate Order of Attributes with a DN is Incorrect

4 Bugs Fixed in this Release

5 Documentation Changes

- Information about third-party modules missing in Administrator's Guide for Oracle HTTP Server

- Terminating SSL Requests Section is Misplaced in Administrator's Guide for Oracle HTTP Server

- Incorrect path specified for mod_wl_ohs.conf file in Using Oracle WebLogic Server Proxy Plug-Ins Guide

- Incorrect Location Entries in Apache Plug-in Sample Codes in Using Oracle WebLogic Server Proxy Plug-Ins Guide

- Incorrect Information about Deprecated Directives for Oracle HTTP Server in Using Oracle WebLogic Server Proxy Plug-Ins Guide

Preface

Oracle HTTP Server 12c(12.1.3) release notes summarizes release information related to issues fixed, general issues and their workarounds, deprecated and removed functionality, and more. This release of the product is in maintenance mode and will no longer have new features or content.

Audience

Oracle HTTP Server is intended for application server administrators, security managers, and managers of databases used by application servers. This documentation is based on the assumption that readers are already familiar with Apache HTTP Server.

Unless otherwise mentioned, the information in this document is applicable when Oracle HTTP Server is installed with Oracle WebLogic Server and Oracle Fusion Middleware Control. It is assumed that readers are familiar with the key concepts of Oracle Fusion Middleware as described in the Understanding Oracle Fusion Middleware Concepts and Understanding Oracle Fusion Middleware.

For information about installing Oracle HTTP Server in standalone mode, see Installing and Configuring Oracle HTTP Server.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following documents in the Oracle HTTP Server documentation set:

- Administering Oracle HTTP Server

- Using Oracle WebLogic Server Proxy Plug-Ins 12.1.3

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Introduction

This chapter introduces the Release Notes for Oracle HTTP Server.

Topics

- Latest Release Information

- Purpose of this Document

- System Requirements and Specifications

- Certification Information

- Product Documentation

- Oracle Support

- Licensing Information

Latest Release Information

This document is accurate at the time of publication. Oracle will update the release notes periodically after the software release. You can access the latest information and additions to these release notes on the Oracle Technology Network at http://www.oracle.com/technetwork/indexes/documentation/index.html.

Purpose of this Document

This document contains information related to the issues and release-specific user information associated with Oracle HTTP Server.

Oracle recommends you review its contents before installing, or working with the product.

System Requirements and Specifications

Oracle HTTP Server installation and configuration will not complete successfully unless users meet the hardware and software pre-requisite requirements before installation. See Oracle Fusion Middleware System Requirements and Specifications.

Certification Information

To see versions of platforms and related software for which Oracle HTTP Server is certified and supported, go to http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html.

Product Documentation

For complete documentation on Oracle HTTP Server go to http://docs.oracle.com/en/middleware/.

Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support at https://support.oracle.com.

Licensing Information

Licensing information for Oracle HTTP Server is available at:

http://oraclestore.oracle.com

Detailed information regarding license compliance for Oracle Fusion Middleware is available at:

http://www.oracle.com/technetwork/middleware/ias/overview/index.html

2 What’s New in this Release

This section describes the new and deprecated features in Oracle HTTP Server.

Topics

- New Features

- Deprecated Features

New Features

The following topics introduce the new and changed features, and other significant changes for the current release of Oracle HTTP Server.

For information about the enhancements, bug fixes, and functional differences between Weblogic Server Proxy Plug-in versions 12.1.1, 12.1.2, and 12.1.3, see My Oracle Support Knowledge Database Doc ID 1111903.1 at http://support.oracle.com.

Topics

- New and Changed Features in 12c (12.1.3)

- New and Changed Features in Release 12c (12.1.2)

New and Changed Features in 12c (12.1.3)

This section contains the following information:

Topics

- New Features in 12c (12.1.3)

- Significant Updates in 12c (12.1.3)

New Features in 12c (12.1.3)

The Oracle WebLogic Server Proxy Plug-In now supports the Websocket protocol. This support adds a new optional directive for the plug-in, WLMaxWebSocketClients. This directive indicates the maximum number of active websocket connections. A connection for regular requests is upgraded to a websocket connection upon client request and is dedicated to websocket processing until the connection is closed. By default, this value is half the total number of configured connections for Oracle HTTP Server.

Significant Updates in 12c (12.1.3)

This section describes features that have been significantly updated from earlier versions of Oracle HTTP Server.

Topics

- SSL FIPS Mode Can Be Configured as a SSLFIPS Directive

SSL FIPS Mode Can Be Configured as a SSLFIPS Directive

In Oracle HTTP Server 12c (12.1.3), you can configure SSL FIPS mode with a SSLFIPS directive, just like Apache open source. For more information on Oracle HTTP Server support for the SSL FIPS mode, see OHS Release 12c (12.1.2) Supports FIPS 140 and Section F.3.6, SSLFIPS.

Note:

For more information on the SSL FIPS 140-2 standard for Oracle HTTP Server 12.1.3, visit https://support.oracle.com and search for Doc ID 2160983.1.

New and Changed Features in Release 12c (12.1.2)

This section contains the following information:

Topics

- New Features in Release 12c (12.1.2)

- Significant Updates in Release 12c (12.1.2)

New Features in Release 12c (12.1.2)

This section describes new features in this version of Oracle HTTP Server.

Topics

- Release 12c (12.1.2) Introduces the WebLogic Management Framework

- OHS Release 12c (12.1.2) Supports FIPS 140

- Search Capability on mod_wl_ohs Configuration Page

- AutoFill Capability on mod_wl_ohs Configuration Page

Release 12c (12.1.2) Introduces the WebLogic Management Framework

This version of Oracle HTTP Server introduces the WebLogic Management Framework, a set of tools that leverage Oracle WebLogic Release 12c (12.1.2) interfaces to provide a simple, consistent and distributed framework for managing Oracle. For more information on the WebLogic Management Framework, see What is the WebLogic Management Framework in Understanding Oracle Fusion Middleware.

The following changes are a result of the new framework:

- Configuration is a post-installation task that begins with creating a domain, primarily by using Configuration Wizard. For more information, see Installing and Configuring Oracle HTTP Server.

- Support for remote management of OHS instances cannot be added after creation. The necessary domain type (WebLogic Server or standalone) should be chosen before installation (see Section 1.4, Domain Types). This is different from Oracle HTTP Server 11g where you could register an Oracle instance with a WebLogic domain at a later time to manage it by using the non-J2EE management tool.

- Configuration files for instances that are part of a WebLogic Server domain are maintained on the administration server node, not on the managed server.

- Changes made to configuration files on the managed server are not preserved when updates are made on the administration server, for example, by using Fusion Middleware Control.

- Command support for managing Oracle HTTP Server is provided primarily within WLST, instead of from the operating system shell. Existing WLST commands and new commands added in this release are applicable to Oracle HTTP Server (see Section 3.6, Using the WebLogic Scripting Tool).

- Server-specific configuration previously maintained in opmn.xml is now configured in ohs.plugins.nodemanager.properties within the Oracle HTTP Server configuration directory.

- When starting or stopping Oracle HTTP Server, console output is now written to the log instead a special console log file.

- Server configuration directories no longer include product code, such as Apache HTTP Server documentation, FastCGI programming libraries, or icon files used by content generated by Oracle HTTP Server. This code resides only in the product directory.

- The administration port, previously referred to as the Proxy MBean or Admin Port, is now used whether the instance is managed as part of a WebLogic Server domain. The port should now be limited to the loopback interface. In the previous release, the administration server would connect to the port.

- The Oracle HTTP Server MBeans, which might be visible in Fusion Middleware Control or WLST, are provided for the use of Oracle management tools. The interfaces are not supported for other use and are subject to change without notice.

OHS Release 12c (12.1.2) Supports FIPS 140

Oracle HTTP Server Release 12c (12.1.2) now complies with the Federal Information Processing Standard publication 140 (FIPS 140). Although the modules used in this version of Oracle HTTP Server are still undergoing their FIPS 140 validation, it uses a version of the underlying SSL libraries that has gone through formal FIPS certification.

As part of Oracle HTTP Server's FIPS 140 compliance, the mod_ossl plug-in now includes the SSLFIPS directive. This directive enables FIPS from Oracle HTTP Server configuration files by toggling the SSL library FIPS_mode flag on or off. SSLFIPS must be set in the global server context and cannot be configured with conflicting settings (for example, SSLFIPS on followed by SSLFIPS off or similar). The mode applies to all SSL library operations.

Note:

Note the following restrictions on SSLFIPS:

- Enabling SSLFIPS mode in Oracle HTTP Server requires a wallet created with AES encrypted (compat_v12) headers. To create a new wallet or to convert an existing wallet with AES encryption, see these sections in orapki in Administering Oracle Fusion Middleware:

- Creating and Viewing Oracle Wallets with orapki

- Creating an Oracle Wallet with AES Encryption

- Converting an Existing Wallet to Use AES Encryption

For more information on SSLFIPS, see Section F.3.6, SSLFIPS.

Search Capability on mod_wl_ohs Configuration Page

When configuring mod_wl_ohs by using Fusion Middleware Control, you can see a list of clusters or servers available to the selected Oracle HTTP Server instance by clicking the Search icon.

Selecting this tool displays a selection dialog box, from which you can select the cluster or server you want to use.

AutoFill Capability on mod_wl_ohs Configuration Page

You can now easily add valid WebLogic Server and endpoint locations for a specified Base URL to the Locations table on the mod_wl_ohs Configuration screen by clicking the AutoFill button. Data for any location of the same name will be updated and any new locations will be added to the table.

Significant Updates in Release 12c (12.1.2)

This section describes features that have been significantly updated from earlier versions of Oracle HTTP Server.

Topics

- WLS Plug-in Logs Are Now Part of the Web Server Logs

- sqlnet.ora NZ Trace Logging Mechanism is No Longer Supported

- Privileged Ports on UNIX Have Different Support Implementation

- ECID Information

- Terminate SSL Requests

WLS Plug-in Logs Are Now Part of the Web Server Logs

The WebLogic Server plug-in logs are now part of the Oracle HTTP Server error log and are prefixed with weblogic: to easily identify them. Hence the directives WLLogFile and Debug are deprecated. If the configuration still uses any of these directives, the following note will appear in the console log file:

The WLLogFile directive is ignored. The web server log file is used instead.
The Debug directive is ignored. The web server log level is used instead.

sqlnet.ora NZ Trace Logging Mechanism is No Longer Supported

Oracle HTTP Server no longer supports the sqlnet.ora NZ trace logging mechanism. As of version Release 12c (12.1.2), you should use the new SSLNZTraceLogLevel directive to enable NZ trace logging using ssl.conf file. For more information, see Section F.3.9, SSLTraceLogLevel.

Privileged Ports on UNIX Have Different Support Implementation

Support for listening on privileged ports on UNIX has a different implementation that does not require running any Oracle HTTP Server code as root. The User and Group directives no longer have to be configured.

ECID Information

In this release of Oracle HTTP Server, you can configure the server to record Execution Context ID (ECID) information in error logs and access logs.

Terminate SSL Requests

In this release of Oracle HTTP Server, you can terminate SSL before or within Oracle HTTP Server. Whether you terminate SSL before the request reaches Oracle HTTP Server or when the request is in the server, depends on your topology.

Deprecated Features

The following features were removed from Release 12c 12.1.3 and 12.1.2.

Topics

- Deprecated Features in 12c (12.1.3)

- Deprecated Features in 12c (12.1.2)

Deprecated Features in 12c (12.1.3)

The following features were removed from Release 12c (12.1.3).

Topics

- Modules Deprecated

- Support for SSL Protocol Version 3 Removed

- The shmht value in SSLSessionCache is Deprecated

Modules Deprecated

The following plug-in modules have been deprecated:

- mod_perl: Allows administrators to run Perl scripts within Oracle HTTP Server.

- mod_fastcgi: Allows administrators to efficiently execute traditional CGI scripts within Oracle HTTP Server.
Oracle is deprecating only the current implementation, the Oracle HTTP Server module (mod_fastcgi) of the FastCGI protocol. Oracle HTTP Server 12.x continues to support the FastCGI protocol by using an alternate implementation, and customers can continue to execute CGI and FastCGI scripts in Oracle HTTP Server 12.x.

- mod_plsql: This module allows administrators to create dynamic web pages from PL/SQL packages and stored procedures.

For more information, visit http://support.oracle.com and search for Oracle Web Tier - Statement of Direction (Doc ID 1576588.1).

Support for SSL Protocol Version 3 Removed

Support for SSL Protocol Version 3 has been removed. Its use is no longer recommended for secure communication.

The shmht value in SSLSessionCache is Deprecated

The shmht value in SSLSessionCache is deprecated.

shmht: /path/to/datafile[bytes]: Uses a high-performance hash table ( bytes specifies approximate size) inside a shared memory segment in RAM, which is established by the /path/to/datafile . This hash table synchronizes the local SSL memory caches of the server processes. Note: in this shm setting, no log files are created under /path/to/datafile on local disk.

Deprecated Features in 12c (12.1.2)

The following features were removed from Release 12c (12.1.2).

Topics

- Integration with Oracle Web Cache

- mod_oradav

- mod_osso

- SSO Plug-ins for Third-party Web Servers

- Oracle WebLogic Server Proxy Plug-Ins for Third-party Web Servers

- SSL Protocol Version 2 and Export Ciphers

Integration with Oracle Web Cache

Oracle Web Cache is no longer included in Fusion Middleware 12c. Oracle HTTP Server support for integration with Oracle Web Cache has been removed.

mod_oradav

The mod_oradav module is no longer included with Oracle HTTP Server. Customers who require DAV support in Oracle HTTP Server must use a third-party solution, such as the open source module mod_dav.

mod_osso

The mod_osso module is no longer included with Oracle HTTP Server. Oracle WebGate is the recommended replacement. WebGate is now installed with Oracle HTTP Server.

SSO Plug-ins for Third-party Web Servers

The OracleAS Single Sign-On (SSO) plug-ins for IIS and iPlanet are no longer included with Oracle HTTP Server. Oracle WebGate is the recommended replacement.

Oracle WebLogic Server Proxy Plug-Ins for Third-party Web Servers

The proxy plug-ins for IIS and iPlanet are no longer included with Oracle HTTP Server. Customers who require proxy support for those web servers can use any proxy support bundled with the web server or use third-party solutions.

SSL Protocol Version 2 and Export Ciphers

Support for SSL Protocol Version 2 and export ciphers has been removed. Their use is no longer recommended for secure communication.

3 Known Issues and Workarounds

This chapter reviews unresolved issues known to exist in Oracle HTTP Server 12c (12.1.3). It also contains descriptions of unresolved issues known to exist in Oracle HTTP Server 12c (12.1.2).

Topics

- Known Issues in Oracle HTTP Server 12c (12.1.3)

- Known Issues in Oracle HTTP Server 12c (12.1.2)

Known issues in 12c (12.1.2) that have been resolved in Oracle HTTP Server 12c (12.1.3) are described in Bugs Fixed in this Release.

Known Issues in Oracle HTTP Server 12c (12.1.3)

This section contains descriptions of unresolved issues known to exist in Oracle HTTP Server 12c (12.1.3).

Topics

- Start and Stop Scripts Require Directory Write Permission

- Oracle HTTP Server Instance Fails To Load mod_cgid

- Continuously Hitting Web Application Through OHS on IBM-AIX Might Generate a Large Error Log

- Configuring Certain Protocols and Ciphers Is Not Allowed

- Starting Node Manager in Collocated Environment Generates System Messages

- Oracle HTTP Server in FMW Control Does Not Recognize Deployer Role

- ServerName Directive Does Not Support IPv6

- Bad CLASSPATH Environment Variable Can Break WLST

- Oracle HTTP Server Configuration Assistant Launcher Fails on Solaris 5.10

- Disable SSL Security Protocols

- Default Value for the MaxPostSize Web Server Plug-in Parameter has Changed

- FIPS is Not Available on the Windows Platform

- Installing Oracle HTTP Server on Oracle Linux 7 Environments

- SSL Certificate Order of Attributes with a DN is Incorrect

Start and Stop Scripts Require Directory Write Permission

Issue

Impacted Platforms: Generic

The startComponent.sh and stopComponent.sh scripts fail when executed from a directory without write permission.

Workaround

To avoid this situation, execute startComponent.sh or stopComponent.sh from $DOMAIN_HOME/bin/ or any other directory with write permission.

Oracle HTTP Server Instance Fails To Load mod_cgid

Issue

Impacted Platforms: Generic

While launching Oracle HTTP Server instance, this message appears:

Couldn't set permissions on unix domain socket

in Oracle HTTP Server Instance log while loading the cgid module (mod_cgid). This message indicates that the mod_cgid is not loaded because the cgisock log file path length exceeds the actual character array length of sun_path variable defined in /usr/include/sys/un.h.

Workaround

To work around this issue, edit the httpd.conf file for the instance and set the Scriptsock value to /var/tmp/cgisock instead of ${ORACLE_HOME}/network/log/cgisock. You can find the httpd.conf file in $DOMAIN_HOME/config/fmwconfig/components/OHS/instances/$INSTANCE_NAME/httpd.conf

Continuously Hitting Web Application Through OHS on IBM-AIX Might Generate a Large Error Log

Issue

Impacted Platforms: Generic

IBM-AIX users continuously hitting a web application that has many users (for example, more than 400) through Oracle HTTP Server might experience a large error log being generated. This is most likely a tuning issue that can be corrected by updating certain IBM-AIX system parameters and Oracle HTTP Server tuning parameters, as described as shown in the following examples.

Workaround

This is most likely a tuning issue that can be corrected by updating certain IBM-AIX system parameters and Oracle HTTP Server tuning parameters, as described as shown in the following examples.

For AIX system parameters:

In /etc/security/limits, should have the following parameters:

nofiles = -1
nofiles_hard = -1

In /etc/rc.net, should have the following parameters:

/usr/sbin/no -o sb_max=6192000
/usr/sbin/no -o tcp_sendspace=4096000
/usr/sbin/no -o tcp_recvspace=4096000
/usr/sbin/no -o udp_sendspace=65536
/usr/sbin/no -o udp_recvspace=655360
/usr/sbin/no -o rfc1323=1
/usr/sbin/no -o ipqmaxlen=150
/usr/sbin/no -o clean_partial_conns=true

You will need to restart your machine.

For Oracle HTTP Server Configuration:

In mod_wl_ohs.conf, should look like the following: example:

LoadModule weblogic_module   "${PRODUCT_HOME}/modules/mod_wl_ohs.so"
# This empty block is needed to save mod_wl related configuration from EM to this file when changes are made at the Base Virtual Host Level

<IfModule weblogic_module>#      WebLogicHost <WEBLOGIC_HOST>#      WebLogicPort <WEBLOGIC_PORT>#      MatchExpression *.jspWebLogicCluster <host-name>:<port>,<host-name>:<port>,<host-name>:<port>ConnectTimeoutSecs 99999 //[Optional parameter]WLIOTimeoutSecs 99999 //[default value 300]WLSocketTimeoutSecs 99999 //[default value 2]MatchExpression *<Location /diagservlet>#      SetHandler weblogic-handler       WLSRequest On       WebLogicCluster<host-name>:<port>,<host-name>:<port>,<host-name>:<port>#      PathTrim /weblogic#      ErrorPage  http:/WEBLOGIC_HOME:WEBLOGIC_PORT/          </Location></IfModule>

In httpd.conf, set the following:

<IfModule mpm_worker_module>
-
-
-
MinSpareThreads     200 [default value 25]
MaxSpareThreads     800 [default value 75]
-
-
-
-
</IfModule>

Configuring Certain Protocols and Ciphers Is Not Allowed

Issue

Impacted Platforms: Generic

If you are using Fusion Middleware Control or WLST commands to configure SSL for Oracle HTTP Server, you cannot configure the TLSv1.1(nzos_Version_1_1) and TLSv1.2(nzos_Version_1_2) protocols for the SSLProtocol directive or for these SSLCipherSuite directive ciphers:

- SSL_RSA_WITH_RC4_128_SHA

- SSL_RSA_WITH_RC4_128_MD5

- SSL_RSA_WITH_AES_128_CBC_SHA

- RSA_WITH_AES_128_CBC_SHA256

- RSA_WITH_AES_256_CBC_SHA256

- RSA_WITH_AES_128_GCM_SHA256

- RSA_WITH_AES_256_GCM_SHA384

- ECDHE_ECDSA_WITH_AES_128_CBC_SHA

- ECDHE_ECDSA_WITH_AES_256_CBC_SHA

- ECDHE_ECDSA_WITH_AES_128_CBC_SHA256

- ECDHE_ECDSA_WITH_AES_256_CBC_SHA384

- ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

- ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

- ECDHE_RSA_WITH_AES_128_CBC_SHA

- ECDHE_RSA_WITH_RC4_128_SHA

- ECDHE_RSA_WITH_3DES_EDE_CBC_SHA

If SSL is enabled for Oracle HTTP Server Virtual Hosts or the SSL configuration has been modified from the SSL Configuration page of Fusion Middleware Control configuration screen or WLST commands, the configuration of the above listed protocols and ciphers in ssl.conf will be lost.To make any changes related to the SSL configuration for these protocols and ciphers, edit ssl.conf directly by using the Advanced Configuration page in Fusion Middleware Control.

Workaround

No workaround available

Starting Node Manager in Collocated Environment Generates System Messages

Issue

Impacted Platforms: Generic

In a collocated environment, when connecting to Node Manager by using the startNodeManger command (for example, when using the startComponent command as in Starting Oracle HTTP Server Instances from the Command Line), you might encounter many system messages upon startup. You can ignore these messages.

Workaround

No workaround available.

Oracle HTTP Server in FMW Control Does Not Recognize Deployer Role

Issue

Impacted Platforms: Generic

In previous releases, a user granted the WLS deployer role was not able to log in to Oracle Fusion Middleware Control. As of Oracle Fusion Middleware Control 12c (12.1.3), the deployer role is supported in JMX Framework and WLS FMW Control EXCEPT Oracle HTTP Server 12.1.3, where FMW Control does not recognize this role. Users granted deployer role will not be able to access Security, Administration or Control functionality.

Workaround

No workaround available

ServerName Directive Does Not Support IPv6

Issue

Impacted Platforms: Generic

The Oracle HTTP Server ServerName directive cannot support IPv6 actual addresses as it does not accept IPv6 addressing format.

Workaround

If you must use IPv6, then create a domain name for the specific IPv6 address and use that in ServerName directive.

Bad CLASSPATH Environment Variable Can Break WLST

Issue

Impacted Platforms: Generic

A bad CLASSPATH environment variable can block the WebLogic Scripting Tool (WLST) from starting. If a bad CLASSPATH is set in your environment variables and you attempt to start WLST, you might see a message like:

Problem invoking WLST - java.lang.NoClassDefFoundError:javax/enterprise/deploy/spi/exceptions/DeploymentManagerCreationException

Workaround

If you encounter a similar error, check your environment variables to see if CLASSPATH is correctly specified.

Oracle HTTP Server Configuration Assistant Launcher Fails on Solaris 5.10

Issue

Impacted Platforms: Generic

While creating an Oracle HTTP Server domain, ORACLE_HOME/ohs/common/bin/config.sh launcher fails and throws this error:

bash-3.2$ ./config.sh
Exception in thread "main" java.lang.InternalError: Can't connect to X11
window server using ':1.0' as the value of the DISPLAY variable.
at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
at
sun.awt.X11GraphicsEnvironment.access$200(X11GraphicsEnvironment.java:65)
at
sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at
sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:74)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:188)

Workaround

If you encounter this problem, apply the respective patch for your platform. These are available from Oracle Support:

- For Solaris.X64, obtain patch 17458572

- For Solaris.SPARC64, obtain patch 17458571

Disable SSL Security Protocols

Issue

Impacted Platforms: Generic

In several places, the Administering Oracle HTTP Server12c documentation discusses the SSL version 3 (SSLv3) security protocol. Because of security concerns, Oracle strongly recommends that you disable the SSLv3 security protocol from Oracle HTTP Server.

To disable SSL security protocols from Oracle HTTP Server:

1. Locate the ssl.conf file in the staging directory and the runtime directory.
You can find the ssl.conf files in the following locations:

Staging directory: DOMAIN_HOME/config/fmwconfig/components/OHS/componentName

Runtime directory: DOMAIN_HOME/config/fmwconfig/components/OHS/instances/componentName

2. Edit the security declaration to use a non-SSL protocol.
For example, to remove the SSLv3 security protocol:

SSLProtocol -SSLv3

or to add the TLS version 1.0 and 1.2 security protocols:

SSLProtocol nzos_Version_1_1 nzos_Version_1_2

or to add the TLS version 1.0, 1.1, and 1.2 security protocols:

SSLProtocol nzos_Version_1_0 nzos_Version_1_1 nzos_Version_1_2

3. Save the files and restart Oracle HTTP Server.

Note:

- If you are editing files manually, ensure you edit a currently configured value instead of adding another. It could be easy to add a global parameter when it will be overridden by a value in the VirtualHost.

- Using the new nzos_Version_* syntax is now preferred. If you are using Oracle Fusion Middleware Control, this is how security will be configured.

Workaround

No workaround available.

Default Value for the MaxPostSize Web Server Plug-in Parameter has Changed

Issue

Impacted Platforms: Generic

The documentation for the MaxPostSize web server plug-in parameter in Oracle Fusion Middleware Using Oracle WebLogic Server Proxy Plug-Ins 12.1.2 and Oracle Fusion Middleware Administering Oracle HTTP Server describes its default value as -1. In this release, the default value has been changed to 0.

Workaround

No workaround available.

FIPS is Not Available on the Windows Platform

Issue

Impacted Platforms: Windows

FIPS is available only on the UNIX/Linux platform. It is not available on the Windows platform. See OHS Release 12c (12.1.2) Supports FIPS 140, SSL FIPS Mode Can Be Configured as a SSLFIPS Directive, and SSLFIPS in Administering Oracle HTTP Server.

Workaround

No workaround available.

Installing Oracle HTTP Server on Oracle Linux 7 Environments

Issue

Impacted Platforms: Oracle Linux

Oracle HTTP Server 12c (12.1.3) can be installed into Oracle Linux 7 (OEL7) environments only if you run the Oracle Universal Installer (OUI) from the command line with the -ignoreSysPrereqs option, for example:

./runInstaller -ignoreSysPrereqs ...

Workaround

No workaround available.

SSL Certificate Order of Attributes with a DN is Incorrect

Issue

Impacted Platforms: Generic

When SSL certificate DN is queried using the CGI interface, the order of attributes of the DN is changed from:

Country, location, Organisation, Organisational Unit, Common Name, Email.

to:

Email, Common Name, Organisational Unit, Organisation, Location, Country.

Workaround

No workaround available.

Known Issues in Oracle HTTP Server 12c (12.1.2)

This section contains descriptions of unresolved issues known to exist in Oracle HTTP Server 12c (12.1.2).

Topics

- Using shutdown() Without Parameters Shuts Down WebLogic Server

- Multiple WLST Versions

- No Command to List All OHS Instances, States, and Ports

- Configuration Wizard Does Not Present a Summary Screen

- Standalone Instances Start in UNKNOWN State

- nmServerStatus() Returns UNKNOWN for Non-existent Instances

- No Automatic Port Allocation for Standalone Instances

- nmStart(), nmServerStatus(), and nmKill() Require ServerType Parameter

- Instances Can Be Deleted in the RUNNING State

- Private Keys Should Not be on a DMZ Machine

- Missing Libraries Might Cause HTTPD to Exit Without Notice

- Create DOMAIN_HOME/servers/<instancename>/logs manually when Diagnosing Start-up Failures

- Installer Sporadically Hangs on Specify Security Updates Screen

- Warning Appears if No Oracle HTTP Server Instance is Created

- Backslashes in Paths in ohs.plugins.nodemanager.properties must be Escaped

- Creating Instance Named "adminserver" Throws Exception

- DMS Displays Incorrect Message if OHS is Down

- Node Manager 12c (12.1.2) OHS Throws Java Exception on AIX

- Set PATH Environment Variable Manually if OHS on Windows Fails to Start

- Recovering Instance on Managed Node Requires tar/untar Commands

- OHS Instance Creation with Config Wizard Does Not Require Machine Assignment

- httpd.exe Fails to Start

- SSLWallet Directive in ssl.conf Might be Saved Incorrectly

- CONFIG_FILE_PATH Setting for apxs in a Standalone Domain

- Create Log Directory Manually When Diagnosing Startup Failures

- createOHSTestDomain() Should be Used Only in Offline Mode

- OHS on UNIX Might Not Start When Listening Port is Configured in Reserved Range

- FIPS is Not Available on the Windows Platform

- SSL Certificate Order of Attributes with a DN is Incorrect

Using shutdown() Without Parameters Shuts Down WebLogic Server

Issue

Impacted Platforms: Generic

The WebLogic Scripting Tool (WLST) command shutdown(<instancename>) is used to stop an Oracle HTTP Server instance in a WebLogic domain. Be aware that using shutdown() with no parameters will shut down the administration server and exit WLST.

Workaround

No workaround available.

Multiple WLST Versions

Issue

Impacted Platforms: Generic

Multiple WLST scripts are provided within an Oracle home. Use the WLST script in ORACLE_HOME/ohs/common/bin, which provides access to Oracle HTTP Server commands and other Fusion Middleware commands.

Workaround

No workaround available.

No Command to List All OHS Instances, States, and Ports

Issue

Impacted Platforms: Generic

This version of Oracle HTTP Server has no command to list all Oracle HTTP Server instances, states and ports. This is different than Oracle HTTP Server 11g, where such information was available by using the command opmnctl status.

Workaround

No workaround available.

Configuration Wizard Does Not Present a Summary Screen

Issue

Impacted Platforms: Generic

When using the Configuration Wizard to create or update a standalone domain, the Configuration Wizard does not present a Configuration Summary Screen. The user does not have the option to go back and make changes.

Workaround

No workaround available.

Standalone Instances Start in UNKNOWN State

Issue

Impacted Platforms: Generic

All standalone Oracle HTTP Server instances created by using the Configuration Wizard start in state UNKNOWN.

Workaround

No workaround available.

nmServerStatus() Returns UNKNOWN for Non-existent Instances

Issue

Impacted Platforms: Generic

In the standalone mode, using the WLST command nmServerStatus() returns UNKNOWN for non-existent instances (for example, if you have a typo in the serverName= argument). Effectively it cannot distinguish between non-existent instances and instances that really are in UNKNOWN; that is, just after creation, as (see Standalone Instances Start in UNKNOWN State).

Workaround

No workaround available.

No Automatic Port Allocation for Standalone Instances

Issue

Impacted Platforms: Generic

In the standalone mode, there is no automatic port allocation for Oracle HTTP Server instances.

Workaround

No workaround available.

nmStart(), nmServerStatus(), and nmKill() Require ServerType Parameter

Issue

Impacted Platforms: Generic

The offline WLST commands nmStart(), nmServerStatus(), and nmKill(), required for management of standalone Oracle HTTP Server instances, all require the serverType='OHS' parameter when managing Oracle HTTP Server. If the serverType parameter is omitted, the command defaults to 'AdminServer" and error messages might be misleading when managing Oracle HTTP Server instances.

Workaround

No workaround available.

Instances Can Be Deleted in the RUNNING State

Issue

Impacted Platforms: Generic

Currently standalone domain update enables you to delete instances in a RUNNING state. This should not be done as it is harmful to Oracle HTTP Server. All OHS instances should be SHUTDOWN (or UNKNOWN) before deletion.

Workaround

No workaround available.

Private Keys Should Not be on a DMZ Machine

Issue

Impacted Platforms: Generic

The keystores.xml file contains private keys that should not be on a demilitarized zone (DMZ; that is, the zone between the internal and external firewalls) machine.

Workaround

If you unpack a domain on a machine in the DMZ, you must remove keystores.xml from it. To do so, go to $domain/config/fmwconfig/ and, from the command line, use this command:

rm $domain/config/fmwconfig/keystores.xml

Missing Libraries Might Cause HTTPD to Exit Without Notice

Issue

Impacted Platforms: Windows

On the Windows platform, Oracle HTTP Server requires Microsoft Visual C++ run-time libraries to be installed on the system in order to function. If they are not installed, Oracle HTTP Server might exit with no output or generate an error dialog box, depending on registry settings.

Workaround

If Oracle HTTP Server fails to start and no error messages are logged by Oracle HTTP Server in the server error log or in Node Manager logs, follow this procedure to diagnose the problem:

1. Verify that the following run-time library is installed:
Visual C++ Redistributable for Visual Studio 2012 (x64), at

https://www.microsoft.com/en-in/download/details.aspx?id=30679

Note:

After installing this package, install any service packs or other fixes to this package which are recommended by Microsoft.

If this package was not installed previously, try to start Oracle HTTP Server again after installing it.

2. Attempt to start Oracle HTTP Server from a command prompt.

a. Create the DOMAIN_HOME/servers/<ohs-instancename>/logs directory if it has not yet been created by Oracle HTTP Server.

b. Try to start Oracle HTTP Server using Fusion Middleware Control or WLST.

c. Copy the file DOMAIN_HOME/servers/<ohs-instancename>/logs/lastinvocation.log to a new file startohs.cmd.

d. Open a new command prompt and run startohs.cmd in that new command prompt.

e. If it generates error messages after the script runs, use those messages to diagnose the startup failure.

f. If it does not generate error messages after the script runs, proceed to the next step.

Note:

Oracle HTTP Server does not function properly when started from a command prompt in this manner. This mechanism for starting Oracle HTTP Server is for diagnostic purposes only.

3. Collect Windows error information when attempting to start Oracle HTTP Server
Error reporting for Oracle HTTP Server library errors might be inhibited on your system. Refer to the following Microsoft article for information on verifying or correcting error reporting:

"HOWTO: How To Change Hard Error Popup Handling in Windows NT", at

http://support.microsoft.com/kb/128642

If ErrorMode is set to 1, library errors might not be reported for Oracle HTTP Server. Change the mode to 0 to enable hard error pop-ups or change the mode to 2 to enable reporting to the Windows event log.

Note:

If this is changed to 0, set it back to the previous value immediately after collecting diagnostic information as it can result in operational problems if errors occur when the server is unattended.

The recommended setting is 2.

a. Change ErrorMode to the desired value.

b. Try to start Oracle HTTP Server using Fusion Middleware Control or WLST or the startohs.cmd script which was created in the previous step.

c. Check for diagnostic information in a hard error popup or in the Windows event log, depending on the setting of ErrorMode.
To check the Windows event log, open Windows Event Viewer and view the logs for Event Viewer (Local) / Windows Logs / Application

Find the event log entries written at the time of the attempt to start Oracle HTTP Server.

Errors locating run-time libraries might be reported as SideBySide errors with event ids 33 or 35, which text describing the Oracle library attempting to load the library and the specific library being loaded. Example:

level=Error
Source=SideBySide
Event Id = 33
Activation context generation failed for "C:\work\Oracle\MD1212\ORACLE~1\bin\oraiau.dll".
Dependent Assembly Microsoft.VC90.CRT,processorArchitecture="amd64",
publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8" could not be found.
Please use sxstrace.exe for detailed diagnosis.

The indicated library must be installed. This example shows VC90, which is the Visual C++ Redistributable for Visual Studio 2012 (x64) library described in step 1 above.

d. Restore ErrorMode to the previous setting.

Create DOMAIN_HOME/servers/<instancename>/logs manually when Diagnosing Start-up Failures

Issue

Impacted Platforms: Generic

If an Oracle HTTP Server instance does not start and has not been started before, manually create the directory DOMAIN_HOME/servers/<instancename>/logs if it does not exist, then attempt to start the instance again so that all diagnostic information can be written. The log file lastinvocation.log, used for diagnosing some types of startup failures, will not be written if this log directory does not exist.

Workaround

No workaround available.

Installer Sporadically Hangs on Specify Security Updates Screen

Issue

Impacted Platforms: Generic

Occasionally, the Oracle WebLogic Server or Oracle HTTP Server installation process hangs on the Specify Security Updates screen (5 of 9) in the NextGen Oracle Universal Installer (OUI). When this occurs, all of the buttons at the bottom of the OUI screen are disabled and inaccessible and the links to go back in the left-hand pane are similarly inactive.

Workaround

When this situation occurs, you must forcibly exit the installer by pressing CTRL-C in the xterm where you initially launched the installer. You can then restart and walk through the installation normally.

Warning Appears if No Oracle HTTP Server Instance is Created

Issue

Impacted Platforms: Generic

In a WebLogic Server domain, while you are not required to create any Oracle HTTP Server instances, if you do not, you will receive a warning is displayed. You can ignore this warning.

Workaround

No workaround available.

Backslashes in Paths in ohs.plugins.nodemanager.properties must be Escaped

Issue

Impacted Platforms: Windows

Any paths placed in Windows implementations of ohs.plugins.nodemanager.properties that include backslashes must have those backslashes escaped.

Workaround

You must do this manually after upgrading from Oracle HTTP Server 11g where paths with backslashes were migrated from opmn.xml to ohs.plugins.nodemanager.properties.

For example:

environment.TMP = C:\Users\user\AppData\Local\Temp\1

Must be modified manually to:

environment.TMP = C:\\Users\\user\\AppData\\Local\\Temp\\1

Creating Instance Named "adminserver" Throws Exception

Issue

Impacted Platforms: Generic

If you try to create an instance with the name "adminserver", Oracle HTTP Server throws an exception post after which you will not be able to create instances, even if they have valid names. Therefore, do not attempt to create instances that use the same name as a given administration server.

Workaround

No workaround available.

DMS Displays Incorrect Message if OHS is Down

Issue

Impacted Platforms: Generic

If you attempt to obtain metrics when Oracle HTTP Server is not running, DMS will display an incorrect message on displayMetricTables.display:

MetricTables(servers='ohs1',servertype='OHS') Traceback (innermost last):
File "<console>", line 1, in ?
File
"/scratch/oracle/Middleware/oracle_common/common/wlst/OracleDMS.py",
line 67, in displayMetricTables
File
"/scratch/oracle/Middleware/oracle_common/common/script_handlers/oracle

dms_handler.py", line 1105, in oracledmsDisplayMetricTables
File
"/scratch/oracle/Middleware/oracle_common/common/script_handlers/oracle

dms_handler.py", line 648, in oracledmsHandleException
NameError: ora_mbs

Workaround

No workaround available.

Node Manager 12c (12.1.2) OHS Throws Java Exception on AIX

Issue

Impacted Platforms: AIX

When running Oracle HTTP Server on AIX, if ULIMIT values of file handlers are small, Node Manager console/log throws "java.io.IOException: error=24, Too many open files" error on AIX.

Workaround

To resolve the issue, increase the ULIMIT values of file handlers as described here:

1. Log in as the root user.

2. Open /etc/security/limits file.

3. Edit the file and set the following values:

- nofiles=8192

- nofiles_hard=65536

4. Reboot the machine to enable the changes.

Set PATH Environment Variable Manually if OHS on Windows Fails to Start

Issue

Impacted Platforms: Windows

If Oracle HTTP Server fails to start on Windows and no log files are generated, the PATH environment variable must be manually specified.

Workaround

To do so, edit the Oracle HTTP Server nodemanager.properties file for this component (found in the domain directory) by doing the following:

1. Edit config\fmwconfig\components\OHS\ohs1\ohs.plugins.nodemanager.properties.

2. Add the following two lines:

environment.ORACLE_HOME = MW_HOME
environment.PATH =%ORACLE_HOME%\\ohs\\bin;%ORACLE_HOME%\\bin;C:\\Windows;C:\\Windows\\system32

Where MW_HOME is the path to the middle ware install, for example:

environment.ORACLE_HOME = C:\\Oracle\\Middleware\\Oracle_Home

Note that all backslash file separators must be escaped with a backslash.

3. Save the file.

4. For Web Logic Server domains, replicate the changes in the run-time area.
For more information on the nodemanager.properties file, see ohs.plugins.nodemanager.properties in Administering Oracle HTTP Server.

5. Start Oracle HTTP Server as described in Starting Oracle HTTP Server Instances in Administering Oracle HTTP Server.

Recovering Instance on Managed Node Requires tar/untar Commands

Issue

Impacted Platforms: Generic

Use tar/untar commands for recovering an instance on an managed node rather than pack/unpack. Pack/unpack are used for recovery on an administration node. pack/unpack are applicable to just the administration node; managed nodes must use tar/untar.

Workaround

No workaround available.

OHS Instance Creation with Config Wizard Does Not Require Machine Assignment

Issue

Impacted Platforms: Generic

When creating an Oracle HTTP Server instance by using the Configuration Wizard, you do not need to assign it to a machine. This is different behavior than you would experience when creating an instance by using the FMW Control's Create OHS command (described in Creating an Instance by Using Fusion Middleware Control in ), where you are prompted for a machine name.

Workaround

No workaround available.

httpd.exe Fails to Start

Issue

Impacted Platforms: Generic

On some occasions, httpd.exe will fail to start, displaying the following error:

Error: The Side-by-Side configuration information for "ORACLE_HOME\bin\ORAIAU.DLL" contains errors.

This happens if you are missing the SP1 version of the 64-bit redistributable. You can obtain this file at:

http://www.microsoft.com/en-us/download/details.aspx?id=2092

Workaround

No workaround available.

SSLWallet Directive in ssl.conf Might be Saved Incorrectly

Issue

Impacted Platforms: Generic

When updating the SSL wallet in Fusion Middleware Control, the SSLWallet directive in ssl.conf might be saved incorrectly.

Oracle HTTP Server expects something similar to this form:

SSLWallet "${ORACLE_INSTANCE}/config/fmwconfig/components/${COMPONENT_TYPE}/instances/${ COMPONENT_NAME}/keystores/wallet2"

The incorrect directive might look like this:

SSLWallet  "${ORACLE_INSTANCE}/config/fmwconfig/components/${COMPONENT_TYPE}/instances/${COMPONENT_NAME}/keystores//OHS/user_projects/domains/base_domain/config/fmwconfig/components/OHS/ohs1/keystores/wallet2"

This incorrect directive will prevent Oracle HTTP Server from starting successfully and a message similar to the following might appear in the OHS error log if OHS startup fails:

server www.example.com:443 has an invalid wallet:
file:/OHS/user_projects/domains/base_domain/config/fmwconfig/components/OHS/instances/ohs1/keystores//OHS/user_projects/domains/base_domain/config/fmwconfig/components/OHS/ohs1/keystores/wallet2 :: 28759

Workaround

To resolve the issue, use the Advanced Configuration feature in FMW Control to select the file ssl.conf and edit it to correct the SSLWallet directive.

CONFIG_FILE_PATH Setting for apxs in a Standalone Domain

Issue

Impacted Platforms: Generic

The apxs program provided with Oracle HTTP Server supports the -a and -A options for editing the configuration in a standalone domain to include the new module. This feature requires that the CONFIG_FILE_PATH environment variable point to the instance configuration directory.

If CONFIG_FILE_PATH is not set before invoking apxs, the error message might provide incorrect information for setting CONFIG_PATH. For the proper setting of CONFIG_FILE_PATH, see Configuring the Oracle HTTP Server Environment to Use the apxs Script in Administering Oracle HTTP Server.

Workaround

No workaround available.

Create Log Directory Manually When Diagnosing Startup Failures

Issue

Impacted Platforms: Generic

If an Oracle HTTP Server instance does not start and has not been started before, manually create the directory DOMAIN_HOME/servers/<instancename>/logs if it does not exist, then attempt to start the instance again so that all diagnostic information can be written. The log file lastinvocation.log, used for diagnosing some types of startup failures, will not be written if this log directory does not exist.

Workaround

No workaround available.

createOHSTestDomain() Should be Used Only in Offline Mode

Issue

Impacted Platforms: Generic

createOHSTestDomain() is intended only for WLST offline mode. If WLST is currently connected to an administration server, use the WLST command disconnect() to disconnect before using createOHSTestDomain(). If createOHSTestDomain() is used in online mode, the resulting error messages will not describe the usage problem.

Workaround

No workaround available.

OHS on UNIX Might Not Start When Listening Port is Configured in Reserved Range

Issue

Impacted Platforms: UNIX

In some UNIX environments that access their root file system using a link, Oracle HTTP Server might not start even if it is properly configured to listen on a port in the reserved range. This occurs when the /etc/cap.ora file is not located on a locally mounted block device.

Workaround

If you are encountering this problem, contact Release Management and download and apply the Release 12.1.2 backport patch.

FIPS is Not Available on the Windows Platform

Issue

Impacted Platforms: Generic

FIPS is available only on the UNIX/Linux platform. It is not available on the Windows platform. See OHS Release 12c (12.1.2) Supports FIPS 140, SSL FIPS Mode Can Be Configured as a SSLFIPS Directive, and SSLFIPS in .

Workaround

No workaround available.

SSL Certificate Order of Attributes with a DN is Incorrect

Issue

Impacted Platforms: Generic

When SSL certificate DN is queried using the CGI interface, the order of attributes of the DN is changed from:

Country, location, Organisation, Organisational Unit, Common Name, Email.

to:

Email, Common Name, Organisational Unit, Organisation, Location, Country.

Workaround

No workaround available.

4 Bugs Fixed in this Release

This chapter reviews issues known to exist in previous Oracle HTTP Server releases that have now been resolved.

Resolved issues are described in the following table:

Issue

Description

Reported In OHS Version

Create DOMAIN_HOME/servers/<instancename>/logs manually when Diagnosing Start-up Failures

If an Oracle HTTP Server instance does not start and has not been started before, manually create the directory DOMAIN_HOME/servers/<instancename>/logs if it does not exist, then attempt to start the instance again so that all diagnostic information can be written. The log file lastinvocation.log, used for diagnosing some types of startup failures, will not be written if this log directory does not exist.

12.1.2.0.0

Creating Instance Named adminserver Throws Exception

If you try to create an instance with the name adminserver, Oracle HTTP Server throws an exception post after which you will not be able to create instances, even if they have valid names. Therefore, do not attempt to create instances that use the same name as a given administration server.

12.1.2.0.0

SSLWallet Directive in ssl.conf Might be Saved Incorrectly

When updating the SSL wallet in Fusion Middleware Control, the SSLWallet directive in ssl.conf might be saved incorrectly.

12.1.2.0.0

Create Log Directory Manually When Diagnosing Startup Failures

If an Oracle HTTP Server instance does not start and has not been started before, manually create the directory DOMAIN_HOME/servers/<instancename>/logs if it does not exist, then attempt to start the instance again so that all diagnostic information can be written. The log file lastinvocation.log, used for diagnosing some types of startup failures, will not be written if this log directory does not exist.

12.1.2.0.0

WebLogic Plug-in Enabled option incorrectly described as a checkbox.

The WebLogic Plug-in Enabled option on the server and cluster pages was incorrectly described as a checkbox in earlier releases of Using Oracle WebLogic Server Proxy Plug-Ins. The WebLogic Plug-in Enabled option is actually a drop-down list containing three items. For more information, see Prerequisites for Configuring the WebLogic Proxy Plug-In.

12.1.3.0.0

Incorrect location of the EditHttpConf tool on the Windows platform was given in the Installation Guide.

The section Configuring Oracle HTTP Server WebGate for Oracle Access Manager in Installing and Configuring Oracle HTTP Server incorrectly listed the path to the EditHttpConf tool on the Windows platform as Oracle_Home/webgate/ohs/tools/setup/InstallTools/EditHttpConf. This has been corrected to Oracle_Home/webgate/ohs/tools/EditHttpConf.

12.1.3.0.0

5 Documentation Changes

This section describes the changes in Oracle HTTP Server documentation.

Topics

- Information about third-party modules missing in Administrator's Guide for Oracle HTTP Server

- Terminating SSL Requests Section is Misplaced in Administrator's Guide for Oracle HTTP Server

- Incorrect path specified for mod_wl_ohs.conf file in Using Oracle WebLogic Server Proxy Plug-Ins Guide

- Incorrect Location Entries in Apache Plug-in Sample Codes in Using Oracle WebLogic Server Proxy Plug-Ins Guide

- Incorrect Information about Deprecated Directives for Oracle HTTP Server in Using Oracle WebLogic Server Proxy Plug-Ins Guide

Information about third-party modules missing in Administrator's Guide for Oracle HTTP Server

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)

Terminating SSL Requests Section is Misplaced in Administrator's Guide for Oracle HTTP Server

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.

1. Log in to the Oracle WebLogic Server Administration Console.

2. In the Domain Structure pane, expand the Environment node.

3. Click Clusters.

4. Select the cluster to which you want to proxy requests from Oracle HTTP Server.

5. The Configuration: General tab appears.

6. Scroll down to the Advanced section, expand it.

7. Click Lock and Edit.

8. Set the WebLogic Plug-In Enabled to yes.

9. Click Save and Activate the Changes.

10. Restart the servers for the changes to be effective.

Incorrect path specified for mod_wl_ohs.conf file in Using Oracle WebLogic Server Proxy Plug-Ins Guide

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: DOMAIN_HOME/config/fmwconfig/components/OHS/componentName.

Incorrect Location Entries in Apache Plug-in Sample Codes in Using Oracle WebLogic Server Proxy Plug-Ins Guide

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

Incorrect Information about Deprecated Directives for Oracle HTTP Server in Using Oracle WebLogic Server Proxy Plug-Ins Guide

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 ODL-text. However, OraLogSeverity must be set to TRACE:16 instead.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2018, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.