Apache: The Definitive Guide, 2nd Edition
by Ben Laurie and Peter Laurie


This errata page lists errors outstanding in the most recent printing.  

If you have any error reports or technical questions, you can send them to
booktech@oreilly.com.  (Please specify the printing date of your copy.)


This page was updated February 6, 2001.


Here's a key to the markup:

	[page-number]: serious technical mistake
	{page-number}: minor technical mistake
	<page-number>: important language/formatting problem
	(page-number): language change or minor formatting problem
	?page-number?: reader question or request for clarification


CONFIRMED errors:


(27) 4th paragraph: 
change "hundred" to "hundreds"


[68] second prose paragraph:  
should read "Now get into .../sales and again type:"


[68] The "HeaderName" directive covered here should actually be the "Header" 
directive (will be fixed in the 1/01 reprint).  There should also be material 
on the "HeaderName" directive, but we can't insert this in a reprint -- it 
will be fixed in the next edition of this book.  Here is the missing material:

HeaderName

  HeaderName filename
  Server config, virtual host, directory, .htaccess

The HeaderName directive sets the name of the file that will be 
inserted at the top of the index listing. Filename is the name of 
the file to include.  

Apache 1.3.6 and earlier: The module first attempts to include
filename.html as an HTML document, otherwise it will try to include 
filename as plain text. Filename is treated as a filesystem path 
relative to the directory being indexed. In no case is SSI processing 
done. Example:

  HeaderName HEADER

When indexing the directory /web, the server will first look for the
HTML file /web/HEADER.html and include it if found, otherwise it will 
include the plain text file /web/HEADER, if it exists.

Apache versions after 1.3.6: Filename is treated as a URI path 
relative to the one used to access the directory being indexed, and 
must resolve to a document with a major content type of "text" 
(e.g., text/html, text/plain, etc.). This means that filename may 
refer to a CGI script if the script's actual file type (as opposed 
to its output) is marked as text/html such as with a directive like:

  AddType text/html .cgi

Content negotiation will be performed if the MultiViews option is
enabled.

If filename resolves to a static text/html document (not a CGI 
script) and the Includes option is enabled, the file will be processed 
for server-side includes (see the mod_include documentation). This 
directive needs mod_autoindex.