ID: 24053
Comment by: drjay_13 at hotmail dot com
Reported By: jphey at netdoor dot com
Status: Bogus
Bug Type: Scripting Engine problem
Operating System: Linux 2.4.20
PHP Version: 4.3.2
New Comment:
How do I include a file with a querystring in the url and avoide this
error?
Previous Comments:
------------------------------------------------------------------------
[2003-07-08 08:09:43] webmaster at woorihost dot com
php4.3.2 disable include
find function include ....
------------------------------------------------------------------------
[2003-06-19 08:26:24] andy dot roche at igraphicsmedia dot com
I would concer that something has gone wrong with the include AND
require statements. I am getting the stream error message on any that
use a URL to point to them. If the file is local to the page being
processed (i.e. <?php [include/require] ('header.htm'); ?>) then it
won't error out. The error ONLY occurs processing remote addresses
(i.e. <?php [include/require] ('http://somewhere.com/header.htm'); ?>).
Suppressing the error message will only hide the problem, not fix it.
I don't mind not having my visitors see the errors, but it would be
nice to the problem fixed as well.
------------------------------------------------------------------------
[2003-06-15 13:58:40] unknown at yabbse dot org
This is not bogus, I've seen it causing a lot of problems.
Here's a better example. Let's say someone tries to use an avatar on a
forum, and the forum decides to check if that avatar is immensely
huge.
Before, getimagesize would work fine.
Now, it generates a warning - effectively requiring a @ before the
getimagesize, and making previous versions of the forum simply not
work. (the error handler will catch the warning and die.)
-[Unknown]
------------------------------------------------------------------------
[2003-06-09 19:10:54] kriek at jonkriek dot com
I had to form absolute paths out of my relative ones.
------------------------------------------------------------------------
[2003-06-06 15:43:01] admin at 1000rpm dot net
I don't think this should have a bogus status. Have a search for the
error message on google, tons of sites are getting this error. It's
pretty urgent, I'm already getting customers complaining.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/24053
--
Edit this bug report at http://bugs.php.net/?id=24053&edit=1
