Click Add Row to create a new row.

4-16 Oracle Fusion Middleware Administrators Guide for Oracle HTTP Server

4.4.7 Disabling the Options Method

The Options method enables clients to determine which methods are supported by a web server. If enabled, it appears in the Allow line of HTTP response headers. For example, if you send a request such as: ---- Request ------- OPTIONS HTTP1.0 Content-Length: 0 Accept: Accept-Language: en-US User-Agent: Mozilla4.0 compatible; MSIE 6.0; Win32 Host: host123:80 you might get the following response from the web server: ---- Response -------- HTTP1.1 200 OK Date: Wed, 23 Apr 2008 20:20:49 GMT Server: Oracle-Application-Server-11g11.1.1.0.0 Oracle-HTTP-Server Allow: GET,HEAD,POST,OPTIONS Content-Length: 0 Connection: close Content-Type: texthtml Some sources consider exposing the Options method a low security risk because malicious clients could use it to determine the methods supported by a web server. However, because web servers support only a limited number of methods, disabling this method will just slow down malicious clients, not stop them. In addition, the Options method may be used by legitimate clients. If your Oracle Fusion Middleware environment does not have clients that require the Options method, you can disable it by including the following lines in the httpd.conf file: IfModule mod_rewrite.c RewriteEngine on RewriteCond {REQUEST_METHOD} OPTIONS RewriteRule . – [F] IfModule

4.5 Deleting an Oracle HTTP Server Component

This section describes how to delete an Oracle HTTP Server component using opmnctl. You cannot delete an Oracle HTTP Server component using Fusion Middleware Control. To delete an Oracle HTTP Server component using opmnctl: opmnctl deletecomponent -componentName name For example, to delete an Oracle HTTP Server component named ohs2 use the following command: opmnctl deletecomponent -componentName ohs2 5 Managing and Monitoring Server Processes 5-1 5 Managing and Monitoring Server Processes This chapter describes how to manage and monitor Oracle HTTP Server. It discusses the procedures and tools to manage Oracle HTTP Server in your environment. This chapter includes the following sections: ■ Section 5.1, Oracle HTTP Server Processing Model ■ Section 5.2, Monitoring Oracle HTTP Server Performance ■ Section 5.3, Configuring Oracle HTTP Server Performance Directives ■ Section 5.4, Understanding Process Security

5.1 Oracle HTTP Server Processing Model

The following sections explain the processing model for Oracle HTTP Server.

5.1.1 Request Process Model

After Oracle HTTP Server is started, it is ready to listen for and respond to HTTPS requests. The request processing model on Microsoft Windows systems differs from that on UNIX systems. ■ On Microsoft Windows, there is a single parent process and a single child process. The child process creates threads that are responsible for handling client requests. The number of created threads is static and can be configured for performance. ■ On UNIX, there is a single parent process that manages multiple child processes. The child processes are responsible for handling requests. The parent process brings up additional child processes as necessary, based on configuration. Although the server has the ability to dynamically bring up additional child Note: 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 Oracle Fusion Middleware Concepts Guide and the Oracle Fusion Middleware Administrators Guide. For information about installing Oracle HTTP Server in standalone mode, see “Installing Oracle Web Tier Without Oracle WebLogic Server” in the Oracle Fusion Middleware Installation Guide for Oracle Web Tier.