On Mon, Jul 24, 2000 at 05:47:46PM +0200, Eric Cholet wrote:
> I've just committed a change which fixes this. Please try it and let me know
> if it works for you.
It does; now a single global "PerlSetupEnv Off" does the job. Thanks!
--
Roger Espel Llima, [EMAIL PROTECTED]
http://www.iagora.com
> > -Original Message-
> > From: Roger Espel Llima [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, July 07, 2000 5:19 PM
> > To: [EMAIL PROTECTED]
> > Cc: [EMAIL PROTECTED]
> > Subject: PerlSetupEnv is evil
> >
> >
> [snip]
> >
> -Original Message-
> From: Roger Espel Llima [mailto:[EMAIL PROTECTED]]
> Sent: Friday, July 07, 2000 5:19 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: PerlSetupEnv is evil
>
>
[snip]
>
> It also turns out that specifying &qu
In the process of optimizing a mod_perl setup (removing useless system
calls), I just spent a very boring couple hours trying to figure out
just why, when I gave Apache a request for a file that didn't exist, it
would first (as expected) stat() each path component, and then do it
again, skipping t
