<[EMAIL PROTECTED]> schrieb im Newsbeitrag
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> ID: 14563
> User updated by: [EMAIL PROTECTED]
> Reported By: [EMAIL PROTECTED]
> Status: Bogus
> Bug Type: *Configuration Issues
> Operating System: Windows 2000 (Win2K)
> PHP Version: 4.1.0
> New Comment:
> Warning: Failed opening '/apache/htdocs/curl_banking.php' for inclusion
(include_path='.;y:\apache\includes') in Unknown on line 0
>
PHP (on Win32) also responds also with the "Failed opening '/x.php' for
inclusion" message if it can't find the originally called file (try calling
a non-existant php-file), at least with PHP as SAPI, but not as CGI (message
in CGI: Unable to open x.php in Unknown on line 0')
> > 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?
I always had to set '.' in include_path when setting any other value, at
least with SAPI.
I don't have much experience with Apache SAPI, but in IIS PHP has problems
to get the appropriate permissions for include files, specially if the
reside on network shares. In IIS the work around is to let IIS check the
permissions for PHP ('check that file exists'). Only after that PHP is able
to fetch the original file and the includes if the user on which the server
runs has the appropriate permissions.
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
