in reply to MOD_PERL ENV variable unsetting?

If $ENV{MOD_PERL} doesn't exist, it is possible that the second invocation of the URL is not running under MOD_PERL.

Maybe MOD_PERL crashed ? Check your syslog and Apache error.log. (This is just a wild guess).

             My goal ... to kill off the slow brain cells that are holding me back from synergizing my knowledge of vertically integrated mobile platforms in local cloud-based content management system datafication.

Replies are listed 'Best First'.
Re^2: MOD_PERL ENV variable unsetting?
by paulthewalrus (Initiate) on Sep 18, 2013 at 15:23 UTC

    That's an interesting question. I don't see anything in syslog or apache error log mentioning mod_perl (other than in the apache log on startup). Is there anything else I can look at?

      Well here's what I noticed - If I set any $ENV{anything} on Apache startup in Perl code, it gets wiped out after the first use per PID just like the MOD_PERL environment variables, but if I use SetEnv it doesn't.

      I don't know what/why they are being removed -- perhaps it's even in some .so. Regardless, my workaround is to add:

      SetEnv MOD_PERL_API_VERSION 2
      SetEnv MOD_PERL 'mod_perl/2.0.6-rc2'

      to my httpd.conf.

      Thanks.