ID:               38040
 Updated by:       [EMAIL PROTECTED]
 Reported By:      php at jon dot limedaley dot com
-Status:           Open
+Status:           Feedback
 Bug Type:         CGI related
 Operating System: Debian Linux testing
 PHP Version:      5.1.4
 New Comment:

>now seems that php5 is alright
Then please change the version in the report and try 4.4.x snapshot
from http://snaps.php.net instead of some third-party build.


Previous Comments:
------------------------------------------------------------------------

[2006-07-08 20:35:19] php at jon dot limedaley dot com

var_dumps can be found here:
http://jon.limedaley.com/misc/test.php
http://jon.limedaley.com/misc/test.php5
http://jon.limedaley.com/misc/test.php/asd
http://jon.limedaley.com/misc/test.php5/asd

I have been working on seeing if there was a workaround for this, and
it now seems that php5 is alright, but php4 has the wrong data.  I am
quite confused, as I looked at this a week or two ago and the behavior
was different.  There was a debian upgrade to php4 recently, but I
didn't see anything interesting in the changelog.

cgi.fixpathinfo is not defined for php4 or php5, which I think defaults
to 0 for php4 and 1 for php5?

Does php_self and path_info look how you think it should for the four
URLs above?

I think they look alright for php5, but test.php/asd seems to have
php_self set incorrectly?

------------------------------------------------------------------------

[2006-07-08 20:09:29] [EMAIL PROTECTED]

var_dump($_SERVER); ?

------------------------------------------------------------------------

[2006-07-08 19:37:08] php at jon dot limedaley dot com

Description:
------------
This is a duplicate of #31892, but I am not sure if anyone will see
that old bug?  I don't know the code well enough to know if that patch
submitted is perfectly fine to include in the main code.  Can someone
check to see if it looks alright?

I am unable to use php5 in cgi mode due to php_self not being correctly
reported.

I can provide an example or a login if it is unclear what is
happening.

I see Bug #31843, but I don't understand the response.  I should just
change all scripts to not use $php_self?  I guess I could make my own
php_self my appending $SCRIPT_FILENAME.$PATH_INFO?  Is there any reason
why this isn't fixed? ie. does anyone use PHP_SELF in its current form,
who would notice if it was changed back to its old behavior?

Reproduce code:
---------------
echo $_SERVER['PHP_SELF']

Expected result:
----------------
the actual script path.

Actual result:
--------------
NULL


------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=38040&edit=1

Reply via email to