Geoffrey Young wrote:
see the DirectoryIndex documentation - you can specify a URL as well as
individual files, so you can simply point to a mod_perl content handler and
leave mod_autoindex/mod_dir to do what they do best.
if you use DirectoryIndex then just put
DirectoryIndex index.html /yourhandler/
at the topmost level, outside of any vhost directives.
So, just to make sure I understand what you're saying, I'd do something
like this:
<Location /Indexer>
SetHandler perl-script
PerlHandler Some::Perl::Handler
</Location>
DirectoryIndex index.html blah blah /Indexer
And will that still work when vhosts do stuff like this?:
<VirtualHost *>
<LocationMatch ^/.*\.fake_ext$>
SetHandler perl-script
PerlHandler blah
</LocationMatch>
</VirtualHost>
(fake_ext is a fake extension, so there are no real files to correspond.
I assume all will be well and will be playing with it momentarily, Just
wanted to see if there's any pitfalls I should know about it)
--
Rando Christensen
<[EMAIL PROTECTED]>
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
