ID: 23220
Comment by: wtatam at premierit dot com
Reported By: storozhilov at mail dot ru
Status: Assigned
Bug Type: Filesystem function related
Operating System: *
PHP Version: 4CVS
Assigned To: wez
New Comment:
If you apply the patch shown in this script it works perfectly
Why has this not been commited into the main branch for both php 4 and
5 ?
Previous Comments:
------------------------------------------------------------------------
[2004-02-04 18:48:37] douga at accessdata dot com
I am seeing the same error. It appears to be generated after the
following loop has completed. More specifically, the Warning message is
emitted just after the loop terminates.
while( !feof($handle) )
{
echo "Looping to read in all of the reply.<br>";
$reply .= fgets($handle);
}
PHP 4.3.4 compiled with --with-openssl
What other information would be helpful?
------------------------------------------------------------------------
[2004-01-27 12:58:26] admin at jazzfanz dot com
I'm sorry but I can't really tell based on this thread if there was
ever a version of PHP where this problem was corrected. Is there a
version?
I'm on 4.3.3 currently under IPlanet.
Is there a workaround without using cURL?
------------------------------------------------------------------------
[2004-01-12 06:42:19] [EMAIL PROTECTED]
Keep it assigned to the only person who can fix it..
------------------------------------------------------------------------
[2004-01-11 11:01:06] [EMAIL PROTECTED]
This bug is apparently still living; even in PHP 5.0b3...
------------------------------------------------------------------------
[2004-01-08 06:14:58] a at anseljh dot com
Red Hat 9
PHP 4.3.4, Apache 2.0.48, OpenSSL 0.9.7c (built from source)
Also happens with either fread() or feof() on an SSL socket connection
opened with fsockopen ($request):
while (!feof($request)) $response .= fread($request, 4096);
This code works flawlessly on a non-SSL socket connection.
------------------------------------------------------------------------
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/23220
--
Edit this bug report at http://bugs.php.net/?id=23220&edit=1
