If you can't configure Apache, your hands are kind of tied. The usual configuration of PHP is to only parse files with the extention of '.php'.
There's probably not such a clear standard when running under mod_perl, but it's quite simple to configure Apache to only run files that end in say '.cgi' under Apache::Registry:
<LocationMatch *.cgi> SetHandler perl-script PerlHandler Apache::Registry </LocationMatch>
(That's probably not the most efficient way to do it, but with Apache TMTOWTDI :) Another alternative would be to put all your scripts into one directory and set the location to that.)
If you're not really able to do much with the config (apart from the fact that you should be complaining to management that your work environment is preventing you from doing your job properly) the perfomance loss at having to run everything under Apache::Registry may be neglible, ie. it may not be enough by itself to swing the pendulum from Perl to PHP
In reply to Re: mod_perl without separate config for static HTML?
by Mutant
in thread mod_perl without separate config for static HTML?
by gunzip
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |