[BlueOnyx:26652] Re: URL_fopen setting not taking effect on 5210R?

[Chris Gebhardt - VIRTBIZ Internet]

Hi Michael,

> In general the "Allow URL fopen" and "Allow URL include" switches in 
> the GUI work well. Both on the Server and Vsite level. But depending 
> on the used PHP implementation it goes into various places in the 
> actual configuration.

Agree, it has always been very reliable.


> Confirm that the settings in it match whatever you have configured in 
> the GUI. In this example I specifically configured the (unsafe) "On" 
> value:
>
> [root at 5210r wwwroot]# cat php.ini |grep allow_url
> allow_url_fopen = On
> allow_url_include = On
>
> Make sure Apache has had time to restart or restart it manually (if 
> you're in a hurry) and then check with a phpinfo() page in the /web 
> directory what PHP reports about the actual state of both flags.
>
Thanks for the tip.  On this advice, I did exactly as suggested and 
changed to suPHP, made the settings change and then waited about 5 
minutes.   It did not change in the php.ini.   I rebooted the server 
just to give everything a kick (big hammer!) and still no change.

[root at server wwwroot]# cat php.ini | grep allow_url
allow_url_fopen = Off
allow_url_include = Off

File shows to be 644, which seems standard after having a quick look at 
another 5210R system:

[root at server wwwroot]# ls -lah php.ini
-rw-r--r-- 1 root root 62K Dec 11 08:41 php.ini

I also see that the file shows to have the immutable bit set, but again, 
that seems to match another randomly checked 5210R system:

[root at server wwwroot]# lsattr php.ini
----i---------e----- php.ini

Am I barking up the wrong tree?

-- 
Chris Gebhardt
VIRTBIZ Internet Services
Access, Web Hosting, Colocation, Dedicated
www.virtbiz.com | toll-free (866) 4 VIRTBIZ