#21410 [Ver]: filetype() shows 'dir' for bogus files on windows
| From: | sniper@php.net | Date: | Thu, 20 Feb 2003 06:09:28 +0000 |
| Subject: | #21410 [Ver]: filetype() shows 'dir' for bogus files on windows | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-33636@lists.php.net to get a copy of this message | ||
ID: 21410
Updated by: sniper@php.net
Reported By: ari at alienhosting dot com
Status: Verified
Bug Type: Filesystem function related
Operating System: win32 only
PHP Version: 4.3.2-dev
New Comment:
Cause of this is that in win32, php_stat() never
tests whether the file exists or not.
Previous Comments:
------------------------------------------------------------------------
[2003-02-19 23:59:50] sniper@php.net
Tested with latest CVS snapshot..
------------------------------------------------------------------------
[2003-01-04 15:30:29] philip@php.net
To be clearer: This happens with any bogus information, whether it be
a string, NULL, or otherwise.
Of course passing no arguments still results in the standard wrong
parameter count error.
------------------------------------------------------------------------
[2003-01-04 15:12:16] philip@php.net
I experience this E_WARNING in linux but in Windows I always get the
following with 4.3.0/win2000:
var_dump( filetype(null) ); // string(3) "dir"
Which seems odd. Basically instead of the E_WARNING error it shows the
bogus file as a dir. This happens with CGI, CLI, and Apache2.
Marking this as a filesystem bug.
------------------------------------------------------------------------
[2003-01-04 14:43:23] nicos@php.net
The documentation now warns about the warnings :-)
Thank you for your report.
------------------------------------------------------------------------
[2003-01-04 14:37:31] nicos@php.net
Changing this bug to a documentation problem.
The warning are now expected for 2 cases: when stat or lstat have
failed and when the file type is unknown.
I'm working on fixing the documentation.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/21410
--
Edit this bug report at http://bugs.php.net/?id=21410&edit=1