ID:               43491
 User updated by:  amccardie at cox dot net
 Reported By:      amccardie at cox dot net
-Status:           Feedback
+Status:           Open
 Bug Type:         Filesystem function related
 Operating System: Windows 2003 SP2
 PHP Version:      5.2-CVS-2007-12-05
 New Comment:

Exactly. The script hangs at the call to file_exists().

Also, using the CLI, the php.exe process goes to 99% CPU time. When it
happens with mod_php, the httpd.exe process hogs the CPU.


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

[2007-12-05 11:03:43] [EMAIL PROTECTED]

So it just hangs there or what? (script never ends)


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

[2007-12-04 16:00:55] amccardie at cox dot net

As suggested, I tried the latest snapshot. I see the same results as
described above. BTW, this happens with the CLI as well as mod_php.

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

[2007-12-04 00:19:33] amccardie at cox dot net

Description:
------------
When open_basedir is set in php.ini, file_exists() will never return if
called with an argument containing a ":/" or ":\\" without a
corresponding drive letter.

Example:

file_exists("C:/foo.txt") => works
file_exists("C:\\foo.txt") => works

file_exists(":/foo.txt") never returns.
file_exists(":\\foo.txt") never returns.

Tested under Windows 2003 Server with SP2 and Windows XP Pro, both
using Apache 2.2.6/mod_php. 

Reproduce code:
---------------
copy php.ini-dist to php.ini
set open_basedir = C:/

<?php
//Should print "no"
print file_exists("C:/foo.txt")?"yes\n":"no\n";

//Should also print "no" but never returns,
//causing high CPU, if open_basedir is set
print file_exists(":/foo.txt")?"yes\n":"no\n";
exit;
?>

Expected result:
----------------
no
no

Actual result:
--------------
no
file_exists() call never returns


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


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

Reply via email to