fopen url wrapper

[Justin Koivisto]

system:
php 4.4.2
windows 2003 server
apache 1.3.x

problem:
scripts don't work :-P

description:

$x='http://exmaple.com/file.txt';

Either:
$content=file_get_contents($x)

Or:
$fp=fopen($x,'r');

[ Would assume this as well:
$content=file($x); ]

When I attempt to access a script on a certain Win2K3 server that
attempts to read a remote file using the fopen url wrappers, I get some
strange results:

Opera (nothing)
MSIE (cannot be reached page [browser default thing])
Firefox (prompt to download)

I sent a head request via lynx, and this is what I get (even after
turning off windows firewall):

Looking up example.com
Making HTTP connection to example.com
Sending HTTP request.
HTTP request sent; waiting for response.
Alert!: Unexpected network read error; connection aborted.
Can't Access `http://example/test.php'
Alert!: Unable to access document.

Everything that I thought of checking in both httpd.conf and php.ini
seem to be just fine.

Does anyone have direction for troubleshooting this?
--
Justin Koivisto, ZCE - ju****@koivi.com
http://koivi.com

[Erwin Moller]

Justin Koivisto wrote:

system:
php 4.4.2
windows 2003 server
apache 1.3.x

problem:
scripts don't work :-P

Right. :P
description:

$x='http://exmaple.com/file.txt';

Either:
$content=file_get_contents($x)

Or:
$fp=fopen($x,'r');

[ Would assume this as well:
$content=file($x); ]

When I attempt to access a script on a certain Win2K3 server that
attempts to read a remote file using the fopen url wrappers, I get some
strange results:

Opera (nothing)
MSIE (cannot be reached page [browser default thing])
Firefox (prompt to download)

I don't think your browser is of any concern.
Your script cannot get the remote contents. This is a PHP-issue, and not a
browser issue.

I sent a head request via lynx, and this is what I get (even after
turning off windows firewall):

Looking up example.com
Making HTTP connection to example.com
Sending HTTP request.
HTTP request sent; waiting for response.
Alert!: Unexpected network read error; connection aborted.
Can't Access `http://example/test.php'
Alert!: Unable to access document.
Good test. :-)

It shows your script hangs.

Did you check the part on fopenwrappers at php.net?
Start here:
http://nl2.php.net/manual/en/ref.fil...llow-url-fopen
[START_QUOTE]

allow_url_fopen boolean

This option enables the URL-aware fopen wrappers that enable accessing
URL object like files. Default wrappers are provided for the access of
remote files using the ftp or http protocol, some extensions like zlib may
register additional wrappers.

Note: This setting can only be set in php.ini due to security
reasons.

Note: This option was introduced immediately after the release of
version 4.0.3. For versions up to and including 4.0.3 you can only disable
this feature at compile time by using the configuration switch
--disable-url-fopen-wrapper.

[END_QUOTE]

So check your php.ini settings first.

If that doesn't help, come back here. :-)

Regards,
Erwin Moller

Everything that I thought of checking in both httpd.conf and php.ini
seem to be just fine.

Does anyone have direction for troubleshooting this?

[Justin Koivisto]

Erwin Moller wrote:

Justin Koivisto wrote:

system:
php 4.4.2
windows 2003 server
apache 1.3.x

description:

$x='http://exmaple.com/file.txt';

Either:
$content=file_get_contents($x)

Or:
$fp=fopen($x,'r');

When I attempt to access a script on a certain Win2K3 server that
attempts to read a remote file using the fopen url wrappers, I get some
strange results:

Opera (nothing)
MSIE (cannot be reached page [browser default thing])
Firefox (prompt to download)
I don't think your browser is of any concern.
Your script cannot get the remote contents. This is a PHP-issue, and not a
browser issue.

No, the browser shouldn't matter, but I thought maybe someone else had a
similar issue but didn't relate it to the url fopen stuff. If they saw
the browser behavior, it may remind them. ;)

I sent a head request via lynx, and this is what I get (even after
turning off windows firewall):

Looking up example.com
Making HTTP connection to example.com
Sending HTTP request.
HTTP request sent; waiting for response.
Alert!: Unexpected network read error; connection aborted.
Can't Access `http://example/test.php'
Alert!: Unable to access document.

Good test. :-)

It shows your script hangs.

I've been using lynx like this for the last year now, it sure seems to
help cut some time off guess work - especially when you are dealing with
the header() function..
Did you check the part on fopenwrappers at php.net?
Start here:
http://nl2.php.net/manual/en/ref.fil...llow-url-fopen

So check your php.ini settings first.

That was the first thing I checked to no avail. It was set correctly,
but I modified the file, resaved and restarted Apache just to be sure. I
also checked the phpinfo() output to be sure the php.ini file was where
it was expected and that the value of allow_url_fopen was set to On.

--
Justin Koivisto, ZCE - ju****@koivi.com
http://koivi.com

[Erwin Moller]

Justin Koivisto wrote:

<snip>

Did you check the part on fopenwrappers at php.net?
Start here:
http://nl2.php.net/manual/en/ref.fil...llow-url-fopen

So check your php.ini settings first.

That was the first thing I checked to no avail. It was set correctly,
but I modified the file, resaved and restarted Apache just to be sure. I
also checked the phpinfo() output to be sure the php.ini file was where
it was expected and that the value of allow_url_fopen was set to On.

Hi,

Ok, that is clear (and right configured) then.
Last thing I can think of:
I once had excactly the same situation, hanging fopen-wrapper.
In my case it turned out that the page I was trying to grab used some
redirection at the server that fopen-wrapper could not handle.

It boiled down to:
1) Client send request (your php/fopenwrapper)
2) Server answer with 'MOVED PERMANENTLY' or something like that.
3) fopenwrappen got completely confused.

That happened with PHP4.3 I think (not sure).

So my suggestion would be to use you lynx again to check this.
Can it handle the url you are trying to grab?

Regards,
Erwin Moller

[Justin Koivisto]

Erwin Moller wrote:

Justin Koivisto wrote:

<snip>

Did you check the part on fopenwrappers at php.net?
Start here:
http://nl2.php.net/manual/en/ref.fil...llow-url-fopen

So check your php.ini settings first.

That was the first thing I checked to no avail. It was set correctly,
but I modified the file, resaved and restarted Apache just to be sure. I
also checked the phpinfo() output to be sure the php.ini file was where
it was expected and that the value of allow_url_fopen was set to On.

Ok, that is clear (and right configured) then.
Last thing I can think of:
I once had excactly the same situation, hanging fopen-wrapper.
In my case it turned out that the page I was trying to grab used some
redirection at the server that fopen-wrapper could not handle.

It boiled down to:
1) Client send request (your php/fopenwrapper)
2) Server answer with 'MOVED PERMANENTLY' or something like that.
3) fopenwrappen got completely confused.

That happened with PHP4.3 I think (not sure).

So my suggestion would be to use you lynx again to check this.
Can it handle the url you are trying to grab?

Yes, I've checked that before too (it's an XML file BTW):

HTTP/1.1 200 OK
Cache-Control: no-store, no-cache, must-revalidate, post-check=0,
pre-check=0
Pragma: no-cache
Content-Type: text/xml;charset=iso-8859-1
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Server: Microsoft-IIS/6.0
Set-Cookie: PHPSESSID=a3c4ba9f6eb2dfe2d1b4d79230e4e614; path=/
MicrosoftOfficeWebServer: 5.0_Pub
X-Powered-By: ASP.NET
Date: Wed, 22 Feb 2006 15:44:46 GMT
Connection: close
Fun, isn't it? :\

--
Justin Koivisto, ZCE - ju****@koivi.com
http://koivi.com

[Erwin Moller]

Justin Koivisto wrote:

Erwin Moller wrote:

Justin Koivisto wrote:

<snip>

Did you check the part on fopenwrappers at php.net?
Start here:
http://nl2.php.net/manual/en/ref.fil...llow-url-fopen

So check your php.ini settings first.
That was the first thing I checked to no avail. It was set correctly,
but I modified the file, resaved and restarted Apache just to be sure. I
also checked the phpinfo() output to be sure the php.ini file was where
it was expected and that the value of allow_url_fopen was set to On.

Ok, that is clear (and right configured) then.
Last thing I can think of:
I once had excactly the same situation, hanging fopen-wrapper.
In my case it turned out that the page I was trying to grab used some
redirection at the server that fopen-wrapper could not handle.

It boiled down to:
1) Client send request (your php/fopenwrapper)
2) Server answer with 'MOVED PERMANENTLY' or something like that.
3) fopenwrappen got completely confused.

That happened with PHP4.3 I think (not sure).

So my suggestion would be to use you lynx again to check this.
Can it handle the url you are trying to grab?

Yes, I've checked that before too (it's an XML file BTW):

HTTP/1.1 200 OK
Cache-Control: no-store, no-cache, must-revalidate, post-check=0,
pre-check=0
Pragma: no-cache
Content-Type: text/xml;charset=iso-8859-1
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Server: Microsoft-IIS/6.0
Set-Cookie: PHPSESSID=a3c4ba9f6eb2dfe2d1b4d79230e4e614; path=/
MicrosoftOfficeWebServer: 5.0_Pub
X-Powered-By: ASP.NET
Date: Wed, 22 Feb 2006 15:44:46 GMT
Connection: close
Fun, isn't it? :\

Darn. :-/
Sorry mate, I am out of options.

If you find the problem, please repost it here.
Good luck.

Regards,
Erwin Moller

[Justin Koivisto]

Erwin Moller wrote:

Darn. :-/
Sorry mate, I am out of options.

If you find the problem, please repost it here.
Good luck.

I've contacted the ISP requesting remote access to a fresh os install of
the server so I can go through and do the installs myself so I exactly
how the system is set up. ;) We'll see what happens with that as my
client is the only one that is using the server at this time.

--
Justin Koivisto, ZCE - ju****@koivi.com
http://koivi.com

[Justin Koivisto]

Justin Koivisto wrote:

Erwin Moller wrote:

Darn. :-/
Sorry mate, I am out of options.

If you find the problem, please repost it here.
Good luck.

I've contacted the ISP requesting remote access to a fresh os install of
the server so I can go through and do the installs myself so I exactly
how the system is set up. ;) We'll see what happens with that as my
client is the only one that is using the server at this time.

heh - that was the way to go... I have not idea why it wasn't working,
but it must have been something that they had done during their install
at some point.

--
Justin Koivisto, ZCE - ju****@koivi.com
http://koivi.com