php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #18721 open_basedir complained when a non existent path is specified in include_path
Submitted: 2002-08-03 04:52 UTC Modified: 2005-01-31 22:59 UTC
From: jimmy at harlindong dot com Assigned:
Status: No Feedback Package: Safe Mode/open_basedir
PHP Version: 4.2.2 OS: FreeBSD 4.6
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: jimmy at harlindong dot com
New email:
PHP Version: OS:

 

 [2002-08-03 04:52 UTC] jimmy at harlindong dot com
As the title says, when there is a non existent path specified in include_path, activating open_basedir will generate the warning

Warning: open_basedir restriction in effect. File is in wrong directory in "xxxxxx.php" on line XX

This warning will not appear if the invalid path does not start with a slash.

e.g. include_path = ".:asdf/asdf:/usr/local/lib/php" will not produce warning when open_basedir is enabled but will produce warning when include_path = ".:/asdf/asdf:/usr/local/lib/php"

note the /asdf/asdf is the non-existent path.

I understand that by removing the non-existent path, the error will be gone, however I think the warning should not have appeared especially when it complains about open_basedir and not about the include_path itself which will cause confusion.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-10-04 11:19 UTC] iliaa@php.net
Please try using this CVS snapshot:

  http://snaps.php.net/php4-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-latest.zip


 [2002-10-20 23:17 UTC] sniper@php.net
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.


 
PHP Copyright © 2001-2018 The PHP Group
All rights reserved.
Last updated: Mon Dec 17 02:01:26 2018 UTC