Bug #14563 Updated: include_path in Apache SAPI on Win2K very broken...
| From: | garth at utmail dot to | Date: | Mon, 17 Dec 2001 16:53:06 +0000 |
| Subject: | Bug #14563 Updated: include_path in Apache SAPI on Win2K very broken... | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-74170@lists.php.net to get a copy of this message | ||
ID: 14563
User updated by: garth@utmail.to
Reported By: garth@utmail.to
Status: Bogus
Bug Type: *Configuration Issues
Operating System: Windows 2000 (Win2K)
PHP Version: 4.1.0
New Comment:
> There is no specific need to set it to ".". It's the default.
If it is the same as the default, shouldn't it work?
If I can't get
include_path="."
to work under Win2K SAPI, how would
include_path=".;C:\PHP\includes"
ever be able to function?
Previous Comments:
------------------------------------------------------------------------
[2001-12-17 11:53:00] sander@php.net
Windows NT & 2000 have a permission-system (NTFS). Check it out.
------------------------------------------------------------------------
[2001-12-17 11:42:15] derick@php.net
There is no specific need to set it to ".". It's the default.
------------------------------------------------------------------------
[2001-12-17 11:35:19] garth@utmail.to
When my PHP.ini is set with:
include_path =
-> I have no problems with SAPI version
When it is set to:
include_path = "."
-> It gives that error...
I don't understand how this could be a permissions
issue, why would the web server be able to read the
file when include_path is blank but not when the
include_path is set to the local directory?
I've seen the error on UNIX systems when you have
a file set to 600, but this is Win2K.
------------------------------------------------------------------------
[2001-12-17 11:06:12] sander@php.net
(reclassified for the stats ;)
------------------------------------------------------------------------
[2001-12-17 11:04:46] sander@php.net
This is a problem with your permissions. Check if the webserver has read access to the file.
------------------------------------------------------------------------
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/?id=14563
Edit this bug report at http://bugs.php.net/?id=14563&edit=1