#19426 [Opn->Bgs]: allow_url_fopen is stated to work as On/Off on php.ini
| From: | sniper@php.net | Date: | Mon, 16 Sep 2002 11:56:08 +0000 |
| Subject: | #19426 [Opn->Bgs]: allow_url_fopen is stated to work as On/Off on php.ini | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-19442@lists.php.net to get a copy of this message | ||
ID: 19426
Updated by: sniper@php.net
Reported By: carenas@chasqui.lared.net.pe
-Status: Open
+Status: Bogus
Bug Type: PHP options/info functions
PHP Version: 4.2.3
New Comment:
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to
report
a bug at http://bugs.php.net/how-to-report.php
Previous Comments:
------------------------------------------------------------------------
[2002-09-16 02:28:38] spic@php.net
Reclassified this as an PHP options bug.
Ain't it?
------------------------------------------------------------------------
[2002-09-16 02:03:00] carenas@chasqui.lared.net.pe
even if php.ini states that this variable is allowed to be "On" or
"Off", there seems to be a different number of possible values (all of
them turning the use of this feature off unless the value is "On").
the problem is that on a phpinfo() call later the value is stated as
"no value" if it is "Off" and taking that this value is supposed to be
"On" on default (like when there is no such configuration on php.ini)
it is misleading.
the reason why it is shown as "no value" when there is an "Off" value
is suspicious, as there is a "no value" clause also when the parameter
is missing alltogether for the configuration file, eventhough the
behaviour is different (if the value is Off the option is disabled, if
the parameter is missing the option is disabled, both showing "no
value" on a phpinfo call tough), sadly i couldn't get to the offending
code on the phpinfo implementation.
also, as phpinfo shows whatever the value is set on php.ini there could
be another posible problem that would need more investigation (like
setting up the variable on a per directory basis to a wrong value using
.htaccess if that is allowed).
not more testing was done to check if the problem could be on the
functions that read the configuration file and therefore more generic
than in this specific case.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=19426&edit=1