ID: 47785
Comment by: andre at webkr dot de
Reported By: andre at webkr dot de
Status: Open
Bug Type: Feature/Change Request
Operating System: Linux
PHP Version: 5.2.9
New Comment:
It's even worse:
When an included file includes another file using a relative path, that
is looked up in the target directory of the symlink!
It should be relative to the path where the symlink resides. The only
access types that should treat the symlink in a special way are unlink
(it should remove the symlink, not the target file) and chmod (it should
do nothing). All other access types (especially the read involved here)
should see the symlink as if it were a file with the content and
attributes of the target file.
Previous Comments:
------------------------------------------------------------------------
[2009-03-26 04:04:41] andre at webkr dot de
Description:
------------
When a symlink is included/required, get_included_files shows the
target of the symlink. Together with Bug #46260 this makes it completely
impossible to determine how the file was really called when it was
included.
Reproduce code:
---------------
include('path_to/a_symlink.php');
var_dump(get_included_files());
Expected result:
----------------
An array containing a string "[...]/path_to/a_symlink.php".
Actual result:
--------------
An array containing a string "[...]/some_file.php".
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=47785&edit=1
