Are you saying that using a mod_perl file extension, eg. .mpl, configured with Apache::Registry will result in static content being handled outside mod_perl? I can mess with httpd.conf to this extent but I'm not in a position to setup separate servers/ports/IPs to separate static HTML requests from mod_perl so your solution may save me from going down the mod_php route. What are the inefficiencies you alluded to?
Are you also saying that configuring a distinct /perl directory for Apache::Registry scripts will leave the static pages to be handled as normal? That's what I normally do anyway?
In reply to Re^2: mod_perl without separate config for static HTML?
by gunzip
in thread mod_perl without separate config for static HTML?
by gunzip
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |