Chapter 14. Apache HTTP Server

183

For more on this topic, refer to the following documentation on the Apache Software Foundation's

website:

http://httpd.apache.org/docs 2.0/mod/core.html#errordocument

14.2.3. Virtual Hosts Configuration

The contents of all

VirtualHost

containers should be migrated in the same way as the main

v

w

server section as described in Section 14.2.2.

Important

Note that SSL/TLS virtual host configuration has been moved out of the main server configuration

file and into /etc/httpd/conf.d/ssl.conf.

For more on this topic, refer to the following documentation on the Apache Software Foundation's

website:

http://httpd.apache.org/docs 2.0/vhosts/

14.2.4. Modules and Apache HTTP Server 2.0

In Apache HTTP Server 2.0, the module system has been changed to allow modules to be chained

together or combined in new and interesting ways. CGI scripts, for example, can generate server 

parsed HTML documents which can then be processed by

mod_include

. This opens up a tremendous

number of possibilities with regards to how modules can be combined to achieve a specific goal.

The way this works is that each request is served by exactly one handler module followed by zero or

more filter modules.

Under Apache 1.3, for example, a PHP script would be handled in its entirety by the PHP module.

Under Apache 2.0, the request is initially handled by the core module   which serves static files  

and is then filtered by the PHP module.

Exactly how to use this and all the other new features of Apache 2.0 for that matter is beyond the

scope of this document; however, the change has ramifications if you have used

PATH_INFO

, which

contains trailing path information after the true filename, in a document which is handled by a module

that is now implemented as a filter. The core module, which initially handles the request, does not by

default understand

PATH_INFO

and will return

404 Not Found

errors for requests that contain such

information. You can use the

AcceptPathInfo

directive to coerce the core module into accepting

requests with

PATH_INFO

. Below is an example of this directive:

AcceptPathInfo on

For more on this topic, refer to the following documentation on the Apache Software Foundation's

website:

http://httpd.apache.org/docs 2.0/mod/core.html#acceptpathinfo

http://httpd.apache.org/docs 2.0/handler.html

http://httpd.apache.org/docs 2.0/filter.html