Geoff,
I ran into some weirdness in this area (on a Win XP machine running Apache 2.0.52)
that seemed to be related to using lowercase environment variable names. It looked as if
PerlSetEnv uppercased the variable names, whereas SetEnv just ignored vars with lower
case names.
Sounds weird I know, and I didn't pin it down exactly, but try uppercase variables and
see if this works for you.
That's probably due to the differences of how perl and Apache interpret environ on win32. mod_perl really calls perl's funcs to get the env. I'm sure if you try that on the command line (plain perl) you will see the same behavior. something like:
setenv foo bar (whatever it is on win32)
perl -le 'print $ENV{FOO}'on unix that won't work, but on win32 it should print 'bar'.
I believe Randy has mentioned this before.
How does mp1 deals with that?
Randy?
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
