ID: 28953 Updated by: [EMAIL PROTECTED] Reported By: mlemos at acm dot org -Status: Open +Status: Bogus Bug Type: Sockets related Operating System: * PHP Version: 4.3.7 New Comment:
Sorry, but your problem does not imply a bug in PHP itself. For a list of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php as this bug system is not the appropriate forum for asking support questions. Thank you for your interest in PHP. Since the user reports that the problem was resolved through an upgrade of the openssl library. I can only assume the problem was with the library and not PHP. Previous Comments: ------------------------------------------------------------------------ [2004-06-29 19:56:04] mlemos at acm dot org I am not sure if this was the problem, but I have updated the OpenSSL installation (openssl-0.9.7b-133 now) with SuSE Linux YAST Online Update program that applies patches that fix bugs and security vulnerabilities and today I am no longer able to reproduce the problem. ------------------------------------------------------------------------ [2004-06-29 19:02:49] [EMAIL PROTECTED] If you're reading data from a M$ server you will encounter this problem; there is not really anything we can do about it, since masking the error will mask legitimate errors. See Bug #23220 ------------------------------------------------------------------------ [2004-06-29 17:41:28] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip Works fine with latest CVS, the provided script returns the following (correct) output: connection opened read 238 bytes read 1000 bytes read 1000 bytes read 1000 bytes read 1000 bytes read 1000 bytes read 1000 bytes read 1000 bytes read 1000 bytes read 1000 bytes read 1000 bytes read 1000 bytes read 1000 bytes read 1000 bytes read 777 bytes reached the end of data ------------------------------------------------------------------------ [2004-06-29 05:41:05] mlemos at acm dot org Description: ------------ It seems that there were changes introduced after PHP 4.3.6, the feof function is no longer returning true when the server closes the SSL socket connection after transmiting all the contents. This seems to make it impossible to determine if there was a real network error or the server closed the connection normally breaking the compatibility of scripts that rely on feof to determine the end of connection condition. This seems to be a revival of bug 25939. It happens under PHp 4.3.2, 4.3.3, 4.3.4 and 4.3.7 . I does not happen under PHP 5.0.0RC3 . Although I could only reproduce it for SSL connections. It may be affecting normal TCP connections but I could not yet produce a test script to demonstrate it consistently. Reproduce code: --------------- <?php $socket=fsockopen("ssl://www.openssl.org", 443, $error); if(!$socket) { echo "socket opening error\n"; exit; } echo "connection opened\n"; if(!fputs($socket, "GET / HTTP/1.1\r\nHost: www.php.net\r\n\r\n")) { echo "socket writing error\n"; exit; } while(!feof($socket)) { $data=fread($socket, 1000); if(!$data) { echo "socket reading error\n"; exit; } echo "read ",strlen($data)," bytes\n"; } echo "reached the end of data\n"; fclose($socket); ?> Expected result: ---------------- connection opened read 574 bytes reached the end of data Actual result: -------------- connection opened read 574 bytes socket reading error ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=28953&edit=1
