ID: 24053
Updated by: [EMAIL PROTECTED]
Reported By: jphey at netdoor dot com
-Status: Bogus
+Status: Assigned
Bug Type: Scripting Engine problem
Operating System: Linux 2.4.20
PHP Version: 4.3.2
-Assigned To:
+Assigned To: wez
New Comment:
Apparently there is still a problem. Will investigate this weekend.
Previous Comments:
------------------------------------------------------------------------
[2003-07-25 03:13:49] ngaugler at ngworld dot net
I want to bring this bug back it, it happens in 4.3.2 when the Zend
Optimizer is installed on the server. When Zend is not, it is fine.
Information is as follows:
Zend Engine v1.3.0, Copyright (c) 1998-2003 Zend Technologies with Zend
Extension Manager v1.0.0, Copyright (c) 2003, by Zend Technologies with
Zend Optimizer v2.1.0, Copyright (c) 1998-2003, by Zend Technologies
------------------------------------------------------------------------
[2003-07-08 17:27:56] drjay_13 at hotmail dot com
How do I include a file with a querystring in the url and avoide this
error?
------------------------------------------------------------------------
[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]
------------------------------------------------------------------------
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
