Oracle is a registered trademark, and the Oracle Logo, Internet Application Server, Oracle9i Application Server, Oracle8i, and PL/SQL are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.

Using the Oracle HTTP Server Powered by Apache with the Oracle9i Database

Oracle 9i Database, Release 9.0.1.0

May 25, 2001

These Release Notes are accurate to the best of our knowledge at the time of going to press. Information that is discovered subsequent to publication will be available through normal support channels.

1 Introduction

The Oracle HTTP Server Powered by Apache has been included as an install option for the Oracle 9i RDBMS. The intended use of the HTTP Server is for use as a development tool/platform and to service lightweight HTTP requests.

The Oracle HTTP Server included with Oracle 9i iAS (Application Server) should be used for full scale production use/deployment of web based services/content.

2 Rights and Restrictions

License Restrictions

The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent and other intellectual and industrial property laws. Reverse engineering, disassembly or decompilation of the Programs is prohibited.

Limitation of Liability

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation.

If the Programs are delivered to the US Government or anyone licensing or using the Programs on behalf of the US Government, the following notice is applicable:

Restricted Rights Notice

Programs delivered subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication and disclosure of the Programs including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, Programs delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication, and disclosure of the Programs shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software - Restricted Rights (June, 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licensee's responsibility to take all appropriate fail-safe, back up, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle Corporation disclaims liability for any damages caused by such use of the Programs.

Third Party Copyright Summary

This product includes software developed by the Apache Group for use in the Apache HTTP Server Project (http://www.apache.org/). This product includes software developed by the Java Apache Project for use in the Apache Jserv servlet engine project (http://java.apache.org/). Apache code is provided "AS IS."

Copyright © 1998-2000 The OpenSSL Project. All rights reserved. This product includes software developed by the OpenSSL project for use in the OpenSSL Toolkit (http://www.openssl.org). This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com). OpenSSL code is provided "AS IS."

Copyright © 1998-2001 Ralf S. Engelschall. All rights reserved. This product includes software developed by Ralf S. Engelschall (rse@engelschall.com) for use in the mod_ssl project (http://www.modssl.org). mod_ssl code is provided "AS IS."

3 Note About Apache JServ Processes

The maximum number of Apache JServ processes supported in an Oracle HTTP Server site has been increased from the Apache distribution default maximum of 25 to a maximum 128. This value is not runtime configurable.

4 JDK/JRE Certification

Oracle has certified the use of both JDK/JRE 1.1.8 and JDK/JRE 1.2.2_07 for building and deploying Java applications with mod_jserv.

For this release, all Java class libraries (e.g., Oracle BC4J [Business Components for Java], Oracle XML Developer's Kit) are shipped compiled with JDK 1.1.8_10. These compiled classes are certified to run under both supported versions of the Java JRE, and they must not be recompiled.

5 Global Server IDs for Oracle HTTP Server Powered by Apache

You can use Global Server IDs to legally upgrade an export-level browser to use high grade encryption (128 bit) if the Apache server contains an appropriate GS-ID certificate and the browser has been patched to accept a GS-ID certificate. While all browsers are shipped with high encryption, it is disabled for export products. Note that with the recent change in US export laws, using GS-ID will not be necessary in the future; for now, however, if you have an export grade browser and require a high level of encryption, follow the steps below to obtain a GS-ID certificate and enable your browser:

Buy a GS-ID Certificate.

Obtain a GS-ID certificate from an appropriate vendor. Oracle has tested the GS-ID certificate from Verisign (http://www.verisign.com/server/prd/g/index.html).

Follow the instructions for downloading and saving the certificate on your server. After obtaining the certificate, the Oracle HTTP Server administrator must update the httpd.conf file. The lines to update are:

SSLCertificateFile <pathname>/gsid.crt 

SSLCertificateKeyFile <pathname>/gsid.key 

SSLCertificateChainFile <pathname>/gsidintermediate.crt

where pathname is the fully qualified path to the installed Verisign file(s).

Buy the Browser Patch.

Obtain a patch that will allow your browser to upgrade the encryption method. Sources include Apache (www.apache.org) and Fortify (www.fortify.net/intro.html). Oracle has tested the patch from Fortify. It straightforward to download and apply to your browser.

6 Selecting a Locale

To select a locale for Oracle HTTP Server installation:

On Solaris 2.6 with Common Desktop Environment (CDE), close all open windows.
Log out (right-click your desktop, select Logout, and click OK).
Select the desired locale from the Options menu. For example, a German locale can be chosen as follows:

Log in (type user name and password).
Open a terminal emulator window.
Type the following command to verify the locale:

env | grep LANG

The output of this command must include the LANG environment variable, and it must have the value selected in Step 3.

If the LANG environment variable is not shown or is set to a different value, check .profile, .login, .cshrc or other files where the LANG environment variable is set or unset. After fixing the problem, repeat these steps, beginning with Step 1.

Install Oracle HTTP Server on Solaris.

The translated files for the selected locale are installed. In addition, English files are always installed.

7 Examples and Demos

Demos and examples for most Oracle HTTP Server components can be found at http://<hostname:port> where hostname is the name of your machine and port is your Oracle HTTP Server listener port. For more information on this port, refer to the Apache documentation.

In addition, examples and demos of Oracle HTTP Server components are provided on your product CD-ROM and installed in the component directories.

8 Known Restrictions and Limitations

Before using Oracle HTTP Server, read through each item in this section to gain an understanding of the restrictions and limitations in this release that may require additional steps.

All Third Party Components

Portions of Oracle HTTP Server are distributed by Oracle under license from third parties ("Third Party Components"), including the Apache Web Server, version 1.3.12, licensed by the Apache Software Foundation. Oracle is distributing these Third Party Components as part of the Oracle 9i RDBMS product and, except as specified herein, will provide standard product support for the Third Party Components, as such support is further defined in the Oracle technical support policies. Please note that Oracle will only support the version of the Third Party Component shipped with Oracle HTTP Server and that other versions which may be freely available on the Internet will not be supported by Oracle.

Oracle may, as a courtesy, refer enhancement requests regarding the Third Party Components to the party who licensed the Component to Oracle; however, Oracle shall have no obligation to do so. In addition, no technical assistance requests will be filed on the non-Third Party Components (the "Oracle Components") unless the problem can be reproduced in an environment consisting of only the Oracle Components.

Apache Modules

Oracle may distribute certain extensions to the Apache Web Server ("Apache Modules") to enhance the functionality provided by the Apache Web Server as part of Oracle HTTP Server. Apache Modules distributed by Oracle are referred to in these Release Notes as Oracle Apache Modules.

Oracle supports the following Oracle Apache Modules in this release:

mod_ssl

SSL support.

mod_perl

Support for writing Apache modules in Perl.

mod_jserv

Communication with servlet engine.

mod_plsql

PL/SQL support.

mod_ose

Delegates URLs to stateful Java and PL/SQL servlets in Oracle Servlet Engine (OSE).

http_core

Core Apache features.

mod_access

Host-based access control; provides access control based on client hostname or IP address.

mod_actions

Filetype/method-based script execution; provides for CGI scripts based on media type or request method.

mod_alias

Aliases and redirects; provides for mapping different parts of the host file system in the document tree, and for URL redirections.

mod_auth

User authentication using text files.

mod_auth_anon

Anonymous user authentication, FTP-style.

mod_autoindex

Automatic directory listings.

mod_cgi

Execution of CGI scripts; processes any file with mime type application/x-httpd-cgi.

mod_define

Configuration definitions.

mod_digest

MD5 authentication; provides for user

authentication using MD5 Digest Authentication.

mod_dir

Basic directory handling; provides for "trailing slash" redirects and serving directory index files.

mod_env

Passing of environments to CGI scripts; provides for passing environment variables to CGI/SSI scripts.

mod_expires

Apply Expires: headers to resources; provides for the generation of Expires headers according to user-specified criteria.

mod_headers

Add arbitrary HTTP headers to resources;

headers can be merged, replaced or removed.

mod_include

Server-parsed documents; provides for

server-parsed HTML documents.

mod_info

Server configuration information; provides a comprehensive overview of the server configuration including all installed modules and directives in the configuration files.

mod_log_config

User-configurable logging replacement for mod_log_common; provides for logging requests made to the server, using the Common Log Format or a user-specified format.

mod_log_referer

Logging of document references; provides for logging the documents that reference documents on the server.

mod_mime

Determining document types using file extensions.

mod_mime_magic

Determining document types using "magic numbers"; can be used to determine the MIME type of a file by looking at a few bytes of its contents.

mod_negotiation

Content negotiation.

libproxy (mod_proxy)

Caching proxy abilities; provides for an HTTP 1.0 caching proxy server.

mod_rewrite

Powerful URL-to-filename mapping using regular expressions; provides a rule-based rewriting engine to rewrite requested URLs on the fly.

mod_setenvif

Set environment variables based on client information; provides for the ability to set environment variables based upon attributes of the request.

mod_so

Support for loading modules at runtime; provides for loading of executable code and modules into the server at start-up or restart time.

mod_speling

Automatically correct minor typographical errors in URLs; attempts to correct misspellings of URLs that users enter, by ignoring capitalization and allowing up to one misspelling.

mod_status

Server status display; allows a server administrator to find out how well the server is performing, presenting an HTML page that gives the current server statistics in an easily readable form.

mod_unique_id

Generate unique request identifier for every request; provides a magic token for each request that is guaranteed to be unique across "all" requests under very specific conditions.

mod_userdir

User home directories; provides for user-specific directories.

mod_usertrack

User tracking using Cookies.

mod_vhost_alias

Support for dynamically configured mass virtual hosting.

Any other Oracle Apache Modules that are included in Oracle HTTP Server are provided "as is" without warranty or support of any kind. Apache Modules from any source other than Oracle, including the Apache Software Foundation or a customer, will not be supported by Oracle.

In addition, Oracle will only provide technical support for problems that can be reproduced with an Apache configuration consisting only of supported Oracle Apache Modules.

8.1 Building mod_perl DBI/DBD-Oracle and Apache::DBI

To build, install, and test mod_Perl DBI/DBD-Oracle and Apache::DBI for the Solaris platform, follow these steps:

Verify that the following software is available in your environment:

C compiler Sun SparcWorks version 5.0

GNU Make GNU Make version 3.77

Perl Perl version 5.005_03

Verify that your PATH environment variable is set correctly to locate the required software.
Install Oracle HTTP Server from your product CD. This version has mod_perl 1.2.4 built in. However, this install does not include the following modules:

Apache::DBI

Perl DBI

Perl DBD-Oracle

Create a symbolic link from your Oracle HTTP Server Apache install directory to /usr/local/apache. For example:

prompt> ln -s /private1/iAS10/Apache /usr/local/apache

Set your PATH environment variable to pick up the correct Perl binaries. For example:

prompt> setenv ORACLE_HOME /private1/iAS10
prompt> setenv PATH ${ORACLE_HOME}/Apache/perl/bin:${PATH}

Note: There are other methods, which include setting the
LD_LIBRARY_PATH and PERL5LIB environment variables, that make mod_perl DBI/DBD-Oracle work. The scope of these steps is limited to one method that has been tested and verified by Oracle.

Download the following modules from http://www.cpan.org/modules/by-module:

DBI version 1.15

DBD-Oracle version 1.0.6

Apache::DBI version 0.87

Unpack the DBI package and follow the README instructions carefully to build, test, and install the module.
The DBD-Oracle module expects enough Oracle software available (such as $ORACLE_HOME/lib, $ORACLE_HOME/rdbms/lib, etc.) to build the driver successfully. Make sure that the following information is available in your environment:

Set the ORACLE_HOME environment variable to point to a valid Oracle HTTP Server install or an Oracle database install (for example, 8.1.6, 8.1.7, etc.).
Set the ORACLE_SID environment variable to point to a valid Oracle SID.
Verify that the LD_LIBRARY_PATH environment variable points to the libclntsh.so. This can be done by setting $ORACLE_HOME/lib in the LD_LIBRARY_PATH environment variable.
If you are using National Language Support (NLS), make sure that you set the ORA_NLS and ORA_NLS33 environment variables to avoid ORA-01019 errors.
Optionally set the ORACLE_USERID environment variable (the tests will use scott/tiger by default).

Unpack the DBD-Oracle package and follow the README instructions carefully to build, test, and install the module.
Unpack the Apache::DBI package and follow the README instructions carefully to build and install the module. There are no tests available for this module yet. This step will install the Apache AuthDBI.pm and DBI.pm modules.
Edit $ORACLE_HOME/Apache/Apache/conf/httpd.conf as follows:

Uncomment the following line (remove the pound sign that is prepended):

PerlModule Apache::DBI

This allows the use of Apache::DBI's persistent database connections. For more information, read the Apache::DBI README instructions, specifically the section on Examples.

Note: httpd.conf is the main Apache server configuration file. Be sure to understand the instructions at the beginning of this file.

Now you are ready to test your persistent connection. As an example, perform the following to test the connection via your startup.pl:

Add this line to your httpd.conf file:

PerlRequire <absolute path to ApacheDBI's startup.pl script>

Modify the startup.pl connect call, such as:

Apache::DBI->connect_on_init('dbi:Oracle:',"scott/tiger", '');

Restart your Oracle HTTP Server:

prompt> $ORACLE_HOME/Apache/Apache/bin/apachectl stop
prompt> $ORACLE_HOME/Apache/Apache/bin/apachectl start

Check Oracle HTTP Server logs to verify that connections were obtained correctly.

Tip: If Oracle HTTP Server logs report that the ORACLE_HOME environment variable is not set, try adding this line to your httpd.conf file:

PerlSetEnv ORACLE_HOME "<absolute path to Oracle Home>"

Another sample Perl script to test the connection is:

##### Perl script start ######
use DBI;
print "Content-type: text/plain\n\n";
$dbh = DBI->connect("dbi:Oracle:", "scott/tiger", "") ||die 
$DBI::errstr;
$stmt = $dbh->prepare("select * from emp order by empno")|| die 
$DBI::errstr;
$rc = $stmt->execute() || die $DBI::errstr;
while (($empno, $name) = $stmt->fetchrow()) { print "$empno
$name\n"; }
warn $DBI::errstr if $DBI::err;
die "fetch error: " . $DBI::errstr if $DBI::err;
$stmt->finish() || die "can't close cursor";
$dbh->disconnect() || die "cant't log off Oracle";
 ##### Perl script End ######

8.2 mod_plsql Requirement

To use the mod_plsql module against a given back-end database, you need to manually install the Oracle PL/SQL Web ToolKit (OWA PL/SQL packages) on the back-end database. The OWA PL/SQL packages should be installed into the SYS database schema; make sure that you have only one installation of the OWA PL/SQL packages. Note that existing Oracle Application Server (OAS) customers upgrading to the Oracle HTTP Server have an older version of these packages that must be replaced.

For more information, see Using the PL/SQL Gateway in the Oracle HTTP Server Documentation Library. Or, you can access the online documentation available at http://hostname.domain:port/pls/admin_/title.htm.

8.3 Restoring Oracle Application Server OWA Packages

When you install the new mod_plsql OWA packages, it places them in the SYS database schema. This can create problems with Oracle Application Server applications using the PL/SQL cartridge. If you experience these problems and want to continue to use your Oracle Application Server PL/SQL cartridge applications, you must recreate the synonyms that reference the Oracle Application Server OWA packages.

To create these synonyms on the origin database machine:

Connect to the origin database as the SYS user in SQL*Plus.
Run the following commands in SQL*Plus. This drops all of the OWA public synonyms created during the Oracle HTTP Server installation process.

drop public synonym OWA_CUSTOM;
drop public synonym OWA_GLOBAL;
drop public synonym OWA;
drop public synonym HTF;
drop public synonym HTP;
drop public synonym OWA_COOKIE;
drop public synonym OWA_IMAGE;
drop public synonym OWA_OPT_LOCK;
drop public synonym OWA_PATTERN;
drop public synonym OWA_SEC;
drop public synonym OWA_TEXT;
drop public synonym OWA_UTIL;
drop public synonym OWA_INIT;
drop public synonym OWA_CACHE;
drop public synonym WPG_DOCLOAD;

Connect to the "oas_public" OWA package installation schema.
Ensure that the user schema has "CREATE PUBLIC SYNONYM" privileges. If it does not, then grant these privileges to the user schema before continuing with the next step.
Run the following commands in SQL*Plus. This recreates the OWA public synonyms so that they reference the Oracle Application Server OWA packages.

create public synonym OWA_CUSTOM for OWA_CUSTOM;
create public synonym OWA_GLOBAL for OWA_CUSTOM;
create public synonym OWA for OWA;
create public synonym HTF for HTF;
create public synonym HTP for HTP;
create public synonym OWA_COOKIE for OWA_COOKIE;
create public synonym OWA_IMAGE for OWA_IMAGE;
create public synonym OWA_OPT_LOCK for OWA_OPT_LOCK;
create public synonym OWA_PATTERN for OWA_PATTERN;
create public synonym OWA_SEC for OWA_SEC;
create public synonym OWA_TEXT for OWA_TEXT;
create public synonym OWA_UTIL for OWA_UTIL;
create public synonym OWA_INIT for OWA_CUSTOM;
create public synonym OWA_CACHE for OWA_CACHE;
create public synonym WPG_DOCLOAD for WPG_DOCLOAD;

8.4 Oracle Demo Certificates Replacement

Oracle Demo certificates (that is, dummy certificates) are included with the Apache build so that the server may be tested in a non-production mode. Before going to production mode, you MUST replace the Oracle Demo certificate with a real certificate.

8.5 Enterprise JavaBean (EJB) Restrictions

In this release, Entity Beans in Enterprise JavaBean (EJB) is not supported. Session Beans are supported only for accessing the middle-tier database.

8.6 New SSL Certificate Required

A new SSL certificate will need to be acquired from Verisign to upgrade from Oracle Application Server (OAS) 4.0.8.2 to Oracle HTTP Server, due to the Spyglass to Apache conversion for listeners.

8.7 OPENSSL Command -CONFIG Option Requirement

The openssl command to create a certificate request or certificate requires the -config option to specify the location of openssl.cnf in $ORACLE_HOME/Apache/open_ssl/bin. Otherwise, the command will fail.

For example:

prompt> openssl req -config $ORACLE_HOME/Apache/Apache/open_ssl/bin -new 
-x509 -days 365 -key ca.key -out ca.crt

8.8 mod_ssl Limitations

In this release, the following algorithms are not supported:

Symmetric encryption algorithms: RC2, RC5, IDEA
Hash algorithm: MD5

8.9 Apache Configuration Error Upon Installation

When installing Oracle HTTP Server Enterprise Edition, and you have installed Apache previously in the same ORACLE_HOME, Apache configuration fails with the following error:

Syntax Error on line 14 of
<ORACLE_HOME>/Apache/Apache/conf/mod__ose.conf 
Aurora Service - directive already effect for this server 
<ORACLE_HOME>/Apache/Apache/bin/httpdsctl start: httpd could not be
started

To work around this error:

Remove the double entry of mod__ose.conf in the file $ORACLE_HOME/Apache/Apache/conf/oracle_apache.conf.
Restart your Oracle HTTP Server:

prompt>$ORACLE_HOME/Apache/Apache/bin/apachectl start

8.10 Errors Starting Apache with "APCHECTL -START" When Using Virtual Hosts

If the port number directive and the NameVirtualHost directive ports do not match, this error will occur. To resolve this issue, make sure that both the port and NameVirtualHost are set to the same port. This can also be resolved by not specifying a port# in the NameVirtualHost directive.

Note that this problem will only occur when starting without SSL.

8.11 Increasing Memory for Apache JServ Applications

If the Apache JServ log or the browser report an "Out Of Memory" condition, the cause is most likely to be that the JVM ran out of memory. This normally happens when data handled by the JVM exceeds its memory allocation pool.

To increase the maximum size of the memory allocation pool for a JVM, use the following steps:

Add this line to

wrapper.bin.parameters=-mx<size>m

<size> is the size, in megabytes, of the memory allocation pool. The default value is 1 megabyte of memory. Oracle recommends that you use a size of 128 megabytes. To set the value to 128 megabytes, add the following line:

wrapper.bin.parameters=-mx<size>m

Restart the Web server after this change so that it can take effect.

8.12 National Language Support (NLS) Considerations

mod_plsql

When configuring mod_plsql, the NLS_LANG environment variable is configured on a per Web server instance level and not at the DAD level.

Ensure that you have the correct NLS_LANG setting before starting your Oracle HTTP Server instance.

Oracle PSP

For Oracle PSP, the NLS_LANG environment variable must be set before loading PL/SQL Server Pages (PSPs) into the database using the loadpsp command.

Using the JDBC OCI8 driver with JServ and OracleJSP

If connecting to Oracle via the JDBC OCI8 driver, the appropriate NLS_LANG setting is required in jserv.properties. For example:

wrapper.env=NLS_LANG=AMERICAN_AMERICA.UTF8

8.13 Configuration of listener.ora for EJBs

In this release, the Oracle HTTP Server installation does not configure the listener.ora file to run Enterprise JavaBeans (EJBs). To run EJBs, you need to configure the listener.ora file as follows:

LISTENER = 
  (DESCRIPTION_LIST = 
    (DESCRIPTION = 
      (ADDRESS_LIST = 
        (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC)) 
      ) 
      (ADDRESS_LIST = 
       (ADDRESS = (PROTOCOL = IPC)(KEY = icache)) 
      ) 

      (ADDRESS_LIST = 
        (ADDRESS = (PROTOCOL = TCP)(HOST = <hostname>)(PORT = 1521)) 
      ) 
    ) 
    (DESCRIPTION = 
      (PROTOCOL_STACK = 
        (PRESENTATION = GIOP) 
        (SESSION = RAW) 
      ) 
      (ADDRESS = (PROTOCOL = TCP)(HOST = <hostname>)(PORT = 2481)) 
    ) 
  ) 

SID_LIST_LISTENER = 
  (SID_LIST = 
    (SID_DESC = 
      (SID_NAME = PLSExtProc) 
      (ORACLE_HOME = <ORACLE_HOME>) 
      (PROGRAM = extproc) 
    ) 
    (SID_DESC = 
       (GLOBAL_DBNAME = icache) 
      (ORACLE_HOME = <ORACLE_HOME>) 
      (SID_NAME = icache) 
    ) 
  )

where <hostname> is the actual hostname of your computer, and <ORACLE_HOME> is the value of your $ORACLE_HOME.

8.14 Oracle XSU Limitations

In this release, the Oracle XML SQL Utility (XSU) does not include the setEncoding method. To download the latest version of XSU that supports encoding functionality, refer to the Oracle Technology Network (OTN) at:

http://technet.oracle.com/tech/xml/oracle_xsu/

8.15 Additional Release Notes

After you install individual Oracle HTTP Server components, the Release Notes for the components are installed in the $ORACLE_HOME/relnotes directory, which contains Release Notes for Oracle HTTP Server, OEM, ASO, JDBC, Net8, OID Client, the RDBMS, SQL*Plus, interMedia, JServer, the precompilers, and SQLJ.

Additionally, component Release Notes and Release Note Addendums are available on the Oracle Technology Network at:

 http://technet.oracle.com/products/ias/

For additional Release Notes, see the following files after installation:

Oracle XML Developer's Kit (XDK)

$ORACLE_HOME/xdk/doc/index.html

OracleJSP

$ORACLE_HOME/jsp/doc/releasenotes_11000.txt

mod_ssl	SSL support.
mod_perl	Support for writing Apache modules in Perl.
mod_jserv	Communication with servlet engine.
mod_plsql	PL/SQL support.
mod_ose	Delegates URLs to stateful Java and PL/SQL servlets in Oracle Servlet Engine (OSE).
http_core	Core Apache features.
mod_access	Host-based access control; provides access control based on client hostname or IP address.

mod_actions	Filetype/method-based script execution; provides for CGI scripts based on media type or request method.
mod_alias	Aliases and redirects; provides for mapping different parts of the host file system in the document tree, and for URL redirections.
mod_auth	User authentication using text files.
mod_auth_anon	Anonymous user authentication, FTP-style.
mod_autoindex	Automatic directory listings.
mod_cgi	Execution of CGI scripts; processes any file with mime type application/x-httpd-cgi.
mod_define	Configuration definitions.
mod_digest	MD5 authentication; provides for user
	authentication using MD5 Digest Authentication.
mod_dir	Basic directory handling; provides for "trailing slash" redirects and serving directory index files.
mod_env	Passing of environments to CGI scripts; provides for passing environment variables to CGI/SSI scripts.
mod_expires	Apply Expires: headers to resources; provides for the generation of Expires headers according to user-specified criteria.
mod_headers	Add arbitrary HTTP headers to resources;
	headers can be merged, replaced or removed.
mod_include	Server-parsed documents; provides for
	server-parsed HTML documents.
mod_info	Server configuration information; provides a comprehensive overview of the server configuration including all installed modules and directives in the configuration files.
mod_log_config	User-configurable logging replacement for mod_log_common; provides for logging requests made to the server, using the Common Log Format or a user-specified format.
mod_log_referer	Logging of document references; provides for logging the documents that reference documents on the server.
mod_mime	Determining document types using file extensions.
mod_mime_magic	Determining document types using "magic numbers"; can be used to determine the MIME type of a file by looking at a few bytes of its contents.
mod_negotiation	Content negotiation.
libproxy (mod_proxy)	Caching proxy abilities; provides for an HTTP 1.0 caching proxy server.
mod_rewrite	Powerful URL-to-filename mapping using regular expressions; provides a rule-based rewriting engine to rewrite requested URLs on the fly.
mod_setenvif	Set environment variables based on client information; provides for the ability to set environment variables based upon attributes of the request.
mod_so	Support for loading modules at runtime; provides for loading of executable code and modules into the server at start-up or restart time.
mod_speling	Automatically correct minor typographical errors in URLs; attempts to correct misspellings of URLs that users enter, by ignoring capitalization and allowing up to one misspelling.
mod_status	Server status display; allows a server administrator to find out how well the server is performing, presenting an HTML page that gives the current server statistics in an easily readable form.
mod_unique_id	Generate unique request identifier for every request; provides a magic token for each request that is guaranteed to be unique across "all" requests under very specific conditions.
mod_userdir	User home directories; provides for user-specific directories.
mod_usertrack	User tracking using Cookies.
mod_vhost_alias	Support for dynamically configured mass virtual hosting.