7 Oracle HTTP Server

This chapter describes issues associated with Oracle HTTP Server. It includes the following topics:

Section 7.1, "General Issues and Workarounds"
Section 7.2, "Configuration Issues and Workarounds"

7.1 General Issues and Workarounds

This section describes general issues and workarounds. It includes the following topics:

Section 7.1.1, "Log Error Message"

7.1.1 Log Error Message

During operations where mod_oc4j calls mod_osso (such as login and logout), the following error message is printed to the Oracle HTTP server log:

[Mon Jun 27 23:57:07 2005] [error] [client 139.185.173.23] [ecid:
90258476571,1] MOD_OC4J_0376: Request initial processing failed in ac worker with
HTTP status code 1. This status will be passed back to the listener for error
handling.

This error message is harmless and can be ignored. It will be removed in a future release.

7.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

Section 7.2.1, "Redirects Break If OracleAS Web Cache is Turned Off or is Disabled"

7.2.1 Redirects Break If OracleAS Web Cache is Turned Off or is Disabled

By default, Oracle HTTP Server sends redirects to the OracleAS Web Cache listening port. If OracleAS Web Cache is not running or is disabled, then redirects from Oracle HTTP Server (and any OC4J application behind Oracle HTTP Server) will not work. If you are not planning to run OracleAS Web Cache, then edit httpd.conf and ssl.conf, changing the Port directive so that it matches the Listen directive instead of the OracleAS Web Cache listening port.