Re: Adding a mod_perl / handler gives odd SCRIPT_NAME and PATH_INFO...
On Tue, 9 Jan 2001 10:45:11 -0500, darren chamberlain wrote: > Jacqui Caren ([EMAIL PROTECTED]) said something to this effect on 01/09/2001: > > > > SetHandler perl-script > > PerlHandler PGC:;Handler > ^ > > > * snip * > > > > SetHandler perl-script > > PerlHandler PGC:;Handler > ^ > > > * snip * > > > > SetHandler perl-script > > PerlHandler PGC:;Handler > ^ > > > > Are these typos in your email or your config? my email - never try and compose email with a migraine :-) The handler works - the problem is that for location / we do not get the rest of the URL as PATh info but the next component of the URL becomes SCRIPT_NAME instead. The location() method example at http://www.modperl.com/book/chapters/ch9.html#Server_Core_Functions probably does what we require - I will try this and see if it can be used to workaround this 'feature' of apache. Thanks, Jacqui
Re: Adding a mod_perl / handler gives odd SCRIPT_NAME and PATH_INFO...
Jacqui Caren ([EMAIL PROTECTED]) said something to this effect on 01/09/2001: > > SetHandler perl-script > PerlHandler PGC:;Handler ^ > * snip * > > SetHandler perl-script > PerlHandler PGC:;Handler ^ > * snip * > > SetHandler perl-script > PerlHandler PGC:;Handler ^ > Are these typos in your email or your config? (darren) -- The world is coming to an end! Repent and return those library books!
RE: Adding a mod_perl / handler gives odd SCRIPT_NAME and PATH_INFO...
> -Original Message- > From: Jacqui Caren [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 09, 2001 8:06 AM > To: Mod Perl > Cc: Oliver Taylor; Jacqui Caren > Subject: Adding a mod_perl / handler gives odd SCRIPT_NAME and > PATH_INFO... > > > > > The problem is that we expect everything after / to be > part of PATH_INFO - from the CGI env it is not possible > to tell if we are trying to exclude / from the dynamic part of > the URL or whether Apache/mod_perl has decided to moe this part > of the URl into the script name. > > Any suggestions are welcome. rewrite requests to / or /index.html to your working - that will keep your dynamic stuff looking like it came from / > > FYI: we have currently modified the sstem to include our own > TransHandler > however for various reasons this is not an ideal solution... if you are already writing your own trans handler, you'll benefit from setting PerlSetupEnv Off and getting $r->path_info yourself instead of gleaning it from %ENV... HTH --Geoff > > Jacqui > >
