No problem... 2.0 gave me a lot of problems (2.0.47), not that I would run
apache2/win32/php-sapi in production for the moment.
as for fopen, if you're intent to try, then:
$fp = fopen ("http://www.example.com/";, "r");
while (!feof($fp)) {
$content .= fread($fp,1024);
}
fclose ($fp);
print $content;
this is just a sanity check to see if the fopen is indeed working with
url_open, or that nothing is blocking the request. Otherwise it could be
just apache2.
"M.R." <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
No, it's not silly, it's a good question, but indeed allow_url_fopen=On,
it's On by default in PHP 4,3 installations.
However, how to fopen eand read a socket via HTTP, I guess my knowlegde
fails as how to accomplish this.
I don't *need* apache 2, I guess, and might install 1.3.28, but for now
don't want to give up too easily on this one, in case it's just a simple
configuration flaw on my part (am newbie).
Thanks very much!
_________________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...>
--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
