, you should understand how the Apache
server works. When Apache receives a request, it processes
it in several stages. First, it translates the URL to the
associated resource (i.e., filename, CGI script, etc.)
on the server machine. Then it checks to see
if the user is authorized to access that resource,
perhaps by requesting and checking an ID and password.
Once the user has passed inspection, the server figures out
what kind of data it's sending back (e.g., it decides a
file ending in
is probably a
At each stage of this process, Apache looks for routines to
"handle" the request. Apache supplies its own handlers;
for example, one of the default handlers is
mod_perl allows you to write your own handlers in Perl, by embedding the Perl runtime library directly into the Apache httpd server executable. To use mod_perl for CGI (which is all that most people want to do with it), you assign the<Location /cgi-bin> ... SetHandler cgi-script ... </Location\>
SetHandler perl-script PerlHandler Apache::Registry
To use other handlers, you don't need to reassign
In order for this to work, mod_perl must have been built with the logging hooks enabled (as described in the previous section), and the Apache::DumpHeaders module must have been installed. mod_perl looks in Apache::DumpHeaders for a routine called<Location /snoop/> PerlLogHandler Apache::DumpHeaders </Location\>
The following is a list of each of the handler directives that
can be enabled by
, and the stages that each is used for.
You can write your own handlers for each of these stages. But there are also dozens of modules that you can download from CPAN, some of which are listed at the end of this chapter.