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
Adding a mod_perl / handler gives odd SCRIPT_NAME and PATH_INFO...
We are working on a dynapage engine that can be operated under mod perl. The system works well when ran under configuration such as SetHandler perl-script PerlHandler PGC:;Handler however when we try to use SetHandler perl-script PerlHandler PGC:;Handler we hit a problem. See the following URls and CGI envs... Url SCRIPT_NAME PATH_INFO --- --- / / / // / / //bbb / /bbb for the folowing config SetHandler perl-script PerlHandler PGC:;Handler we get pretty similar CGI envs 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. FYI: we have currently modified the sstem to include our own TransHandler however for various reasons this is not an ideal solution... Jacqui
