Random notesof Naveen Agnihotri
AOLserver has a much more intuitive API and much better documentation. The user community is much smaller, but ther people involved are active and it doesn't take too long to get questions answered. The only reason I'm not using AOLserver right now is because it doesn't run on my machine, which runs debian on a HPPA processor.
When I started using Apache, I was impressed with how comprehensive the documentation looked, until I tried to do something that wasn't in one of the examples. Here's how it went:
LoadModule perl_module modules/mod_perl.so PerlRequire "/usr/local/apache2/perl/startup.pl"
Apache is made up of a bunch of different modules, which are all documented separately, and if you're trying to make them do something together, then it may or may not work right out of the box. Especially if you're trying to do something that's not directly in the examples. For example, see my experience with the mod_perl script for sending mail below.
Alias /cgi-bin /web/cgi-bin <Location /cgi-bin> SetHandler perl-script PerlResponseHandler ModPerl::Registry Options +ExecCGI </Location>Now all files in the /web/cgi-bin directory will be treated as mod_perl perl scripts. Or so I think.
For example, instead of the usual HTML that would read:
I would like to generate HTML that reads:
The HTML of the email address in the second line reads the same in a web browser as the first line, but cannot be parsed by a web crawler (unless it is enormously sophisticated, and in which case we'll have to think of something else).
Here's how I've implemented this scheme:
<Files ~ "\.html"> PerlOutputFilterHandler MyApache::EmailObfuscate </Files>