Re: Failure remote includes
| From: | Sek-Mun Wong | Date: | Fri, 01 Aug 2003 23:30:01 +0000 |
| Subject: | Re: Failure remote includes | ||
| References: | 1 | Groups: | php.windows |
| Request: | Send a blank email to php-windows+get-20983@lists.php.net to get a copy of this message | ||
M.R.,
my educated guess is that somehow the include code works differently for
php-sapi on apache2. It's not optimal, but unisntall apache2, reinstall
1.3.2x and test it out. (nuke it from orbit, it's the only way to be sure)
"M.R." <purplespirit@hccnet.nl> wrote in message
news:001601c3585a$02faaef0$7142c23e@giga...
As a follow up on my earlier reply, I found out how to read the socket and
GET / HTTP, and that works on the remote files. However, a simple include
doesn't.
_________________Original message_______________
Sek-Mun Wong wrote August 1 2003 8:19 in reply to Re: Failure remote
includes
<..silly one but i assume you already have "allow_url_fopen=On" in php.ini?
(it should tell you anyway, that this is not set, plus the error below)
works for me in 4.3.2/winxp pro/apache 1.3.28.
I guess if you don't *need* apache 2, don't do it.
another test might be to fopen and read a socket via http to make sure your
connection (or I should say apache's service logon user's connection) to the
aforementioned ip/host is ok...>