Bug #15430 Updated: socket_set_blocking doesn't work

ID: 15430 Updated by: on4kst@skynet.be Reported By: armageddon@raydan.de Status: Closed Bug Type: Sockets related Operating System: Windows 2000 PHP Version: 4.1.1 New Comment: In despite of this bug is closed the socket_set_blocking($fp, FALSE) function does not work as reported by armageddon@raydan.de. Tested on Windows XP / Apache / PHP 4.0.6 and PHP 4.2.0. Used with fsockopen and fgets the behaviour in correct when the value is set to TRUE. When FALSE, a fgets() function always returns an empty string EVEN IF A DATA IS PENDING. In other words fgets() stops to read data. Previous Comments: ------------------------------------------------------------------------ [2002-06-18 19:18:33] sniper@php.net This bug has been fixed in CVS. You can grab a snapshot of the CVS version at http://snaps.php.net/. In case this was a documentation problem, the fix will show up soon at http://www.php.net/manual/. In case this was a PHP.net website problem, the change will show up on the PHP.net site and on the mirror sites. Thank you for the report, and for helping us make PHP better. ------------------------------------------------------------------------ [2002-06-08 07:10:59] armageddon@raydan.de Why "Duplicate" ? The other report is about a memory leak and mine is about PHP doesn't read data from the socket when using non-blocking sockets. ------------------------------------------------------------------------ [2002-06-08 06:55:03] mfischer@php.net Wierd duplicate of http://bugs.php.net/?id=15485&edit=1 ------------------------------------------------------------------------ [2002-06-08 06:44:38] bool@boolsite.net It's work for me, but it leaks memory... :o( The problem is analysed actually... :o) ------------------------------------------------------------------------ [2002-04-06 15:05:52] armageddon@raydan.de Re: ruehl@igd.fhg.de This doesn't work for me :-( I still don't get any date when I use non-blocking sockets... ------------------------------------------------------------------------ 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/15430 -- Edit this bug report at http://bugs.php.net/?id=15430&edit=1