Re: [mp2] PerlInitHandler and PATH_INFO weirdness

2004-03-05 Thread Jean-Michel Hiver
Once you run the above at the very beginning of your script, it'll pull out $r out from thin air from that point on. that's exactly what +GlobalRequest does. True, but since it is not necessary to do this first operation with mp1, when you use Apache::compat with mp2 this should be done for

[mp2] PerlInitHandler and PATH_INFO weirdness

2004-03-04 Thread Jean-Michel Hiver
Hi List, I am trying to get a rather large-ish web app to run with apache 2 / mod_perl 1.99. I have installed the latest RPMs for Fedora from FreshRPMs. PerlModule Apache2 PerlModule Apache::compat PerlOptions +GlobalRequest PerlOptions +SetupEnv I have a very strange behavior with

Re: [mp2] PerlInitHandler and PATH_INFO weirdness

2004-03-04 Thread Geoffrey Young
Jean-Michel Hiver wrote: Hi List, I am trying to get a rather large-ish web app to run with apache 2 / mod_perl 1.99. I have installed the latest RPMs for Fedora from FreshRPMs. PerlModule Apache2 PerlModule Apache::compat PerlOptions +GlobalRequest PerlOptions +SetupEnv I

Re: [mp2] PerlInitHandler and PATH_INFO weirdness

2004-03-04 Thread Jean-Michel Hiver
I would consider it a bug, but mod_perl (through the current release) populated %ENV when the first Perl*Handler runs, which may have been before or after translation (which is where path_info becomes known). if you specifically move that PerlInitHandler to a PerlHeaderParserHandler I'd suspect

Re: [mp2] PerlInitHandler and PATH_INFO weirdness

2004-03-04 Thread Geoffrey Young
Jean-Michel Hiver wrote: I would consider it a bug, but mod_perl (through the current release) populated %ENV when the first Perl*Handler runs, which may have been before or after translation (which is where path_info becomes known). if you specifically move that PerlInitHandler to a

Re: [mp2] PerlInitHandler and PATH_INFO weirdness

2004-03-04 Thread Geoffrey Young
We have the way to do it: Apache-server-add_config(['PerlOptions +GlobalRequest +SetupEnv']); But normally, those options are set in httpd.conf's specific containers and not always globally for the whole server. I'm not sure it's a good idea to enforce these settings for the whole

Re: [mp2] PerlInitHandler and PATH_INFO weirdness

2004-03-04 Thread Stas Bekman
Geoffrey Young wrote: We have the way to do it: Apache-server-add_config(['PerlOptions +GlobalRequest +SetupEnv']); But normally, those options are set in httpd.conf's specific containers and not always globally for the whole server. I'm not sure it's a good idea to enforce these settings for

Re: [mp2] PerlInitHandler and PATH_INFO weirdness

2004-03-04 Thread Geoffrey Young
You have the API to do that override already. Add as the first line in your script: $r = shift; Apache-request($r); that's not the same. in mp1 Apache-request is used for pulling $r out of thin air. isn't +GlobalRequest for that exact circumstance, allowing you to get at $r when none is

Re: [mp2] PerlInitHandler and PATH_INFO weirdness

2004-03-04 Thread Stas Bekman
Geoffrey Young wrote: You have the API to do that override already. Add as the first line in your script: $r = shift; Apache-request($r); that's not the same. in mp1 Apache-request is used for pulling $r out of thin air. isn't +GlobalRequest for that exact circumstance, allowing you to get at