www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Lindner <lind...@itu.int>
Subject mod_perl/4636: mod_perl destroys PATH variable for subsequent CGI accesses
Date Wed, 23 Jun 1999 13:37:50 GMT

>Number:         4636
>Category:       mod_perl
>Synopsis:       mod_perl destroys PATH variable for subsequent CGI accesses
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Jun 23 06:40:01 PDT 1999
>Originator:     lindner@itu.int
>Release:        1.3.7-dev
Digital Unix 4.0F, DEC bundled C compiler, switches -fast -O4
Started with httpd -X and a (simple) configuration file.

hitting a mod_perl Registry script (or an Apache::ASP script)
resets the PATH to en empty string in the server, which then screws up the
regular CGI scripts.
I'm slowly simplifying the test case, but it appears that any
mod_perl script will do.
Not sure.  Sorry.
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

View raw message