I've written a PerlHandler module that does some checking, then returns either DECLINED or FORBIDDEN. If it returns DECLINED the uri that was requested gets processed by the content handler and returned. This works as expected if the requested uri is a vanilla .html page. However if the uri is a perl script, instead of the perl script being executed, the source code is returned. Any suggestions how to force Apache to treat the uri like it would have, had I not stuck the PerlHandler in there?
Example of what I mean: -user tries to access www.something.com/page.html -Apache::MyModule does some checking and returns DECLINED -Apache processes page.html and it gets returned to the user as expected -user tries to access www.something.com/page.cgi -Apache::MyModule does some checking and returns DECLINED -Apache processes page.cgi as an .html document and returns the source of page.cgi instead of executing it; BAD! If I disable Apache::MyModule the script gets executed by Apache as expected (in case anyone was going to suggest that I make sure Apache is set up to handle perl scripts correctly; it is). (In case it's suggested, I can't currently use PerlAuthenHandler or any handler other than PerlHandler. The module makes use of mod_ssl environment variables which are not accessible until the PerlHandler phase. I also can't make use of Geoff Young's module that works around this [Apache::SSLLookup] because I'm forced to run Apache 1.3.) Thanks for any help. Jason [EMAIL PROTECTED]
