By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,664 Members | 1,643 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,664 IT Pros & Developers. It's quick & easy.

open_basedir and is_readable

P: n/a
open_basedir exhibits very annoying (and imho buggy) behavior in
generating warnings even when is_readable() is called, rather than
just returning false as appropriate. This means it is impossible to
use is_readable as a precondition before opening a file.

Is there any way to check the preconditions of reading a file without
generating warnings for files outside open_basedir?
Feb 6 '08 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On Feb 6, 2:26*pm, Arancaytar <arancaytar.ilya...@gmail.comwrote:
open_basedir exhibits very annoying (and imho buggy) behavior in
generating warnings even when is_readable() is called, rather than
just returning false as appropriate. This means it is impossible to
use is_readable as a precondition before opening a file.

Is there any way to check the preconditions of reading a file without
generating warnings for files outside open_basedir?
Addendum: http://bugs.php.net/bug.php?id=37476 describes this behavior.
Feb 6 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.