Re: 4.0.1 Release Candidate packaged

From: Date: Mon, 26 Jun 2000 07:39:30 +0000
Subject: Re: 4.0.1 Release Candidate packaged
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-22328@lists.php.net to get a copy of this message
> >[...] > > > >- Fixed problem with CGI crashing on certain servers especially Windows > >Apache > > & O`Reilly website (Andi) > > > >[...] > >My bug report: #4456 and #5163 > > > >Other bug report with suggestion on how to fix it: #5181 > > Can you spell it out. The bug database is down now. Sure, you can find the complete on geocrawler: http://www.geocrawler.com/archives/3/5/2000/6/0/3933680/ [...] The problems are all in the init_request_info() function. Specifically, 1. ~Line 252. script_filename is set to getenv("SCRIPT_FILENAME") rather than getenv("SCRIPT_NAME"). Maybe SCRIPT_FILENAME is a newer variant I haven`t heard of, but our servers have always used SCRIPT_NAME. 2. ~Line 278. If DISCARD_PATH is set and script_filename is available, SG(request_info).path_translated should be set to the concatenation of getenv("DOCUMENT_ROOT") and script_filename, not just script_filename. Otherwise, when php_fopen_primary_script() tries to open it it will bomb, because it doesn`t have the full path. 3. ~Line 290. For some reason, irrespective of the previous DISCARD_PATH section, SG(request_info).path_translated is set to NULL. This will clobber the script name when discard path is enabled. As far as I can tell this line should simply be removed. [...] > >I tried modifying the code without success, PHP3 still runs fins with > >the same setup. I'd really like to help (I've been trying PHP4 since > >Beta1). Compiled as a module, PHP4 runs flawlessly but I really need to > >make it work through suEXEC so discard_path is needed. > > What is the exact behavior discard_path should have? > Let me know what it's supposed to do and I'll look into it later on. I don't really know, I'd like it to behave like PHP3 :) (in fact, like Perl, Python, etc.) Maybe I can print out the different related variables like path_translated, etc. to see what goes wrong, is there a special PHP debug function that can print out these or should I use printf() ? -- Olivier.Cahagne@epita.fr

« previous php.dev (#22328) next »