Red Hat ENTERPRISE LINUX 5 - DEPLOYMENT Deployment Manual page 337

http://httpd.apache.org/docs-2.0/mod/mod_negotiation.html#cachenegotiateddocs
•
22.2.2.2.5. Error Documents
To use a hard-coded message with the ErrorDocument directive, the message should be enclosed
in a pair of double quotation marks ", rather than just preceded by a double quotation mark as
required in Apache HTTP Server 1.3.
For example, the following is a sample Apache HTTP Server 1.3 directive:
ErrorDocument 404 "The document was not found
To migrate an ErrorDocument setting to Apache HTTP Server 2.0, use the following structure:
ErrorDocument 404 "The document was not found"
Note the trailing double quote in the previous ErrorDocument directive example.
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
•
22.2.2.3. Virtual Host Configuration
The contents of all <VirtualHost> containers should be migrated in the same way as the main
server section as described in
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.
http://httpd.apache.org/docs-2.0/vhosts/
•
22.2.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. Common Gateway Interface (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 HTTP Server 1.3, for example, a Perl script would be handled in its entirety by the
Perl module (mod_perl). Under Apache HTTP Server 2.0, the request is initially handled by the core
module — which serves static files — and is then filtered by mod_perl.
Exactly how to use this, and all other new features of Apache HTTP Server 2.0, is beyond the scope
of this document; however, the change has ramifications if the PATH_INFO directive is used for a
Migrating Apache HTTP Server 1.3 Configuration Files to 2.0
Section 22.2.2.2, "Main Server Configuration".
311