#35086 [Fbk->Opn]: socket_read does not return empty string after receiving '\n'
ID: 35086
User updated by: jelte dot werkhoven at cruisetravel dot nl
Reported By: jelte dot werkhoven at cruisetravel dot nl
-Status: Feedback
+Status: Open
Bug Type: Sockets related
Operating System: GNU/Linux (SuSE 10.0)
PHP Version: 4.4.1
New Comment:
PHP 5.1.0RC5-dev (cli) (built: Nov 8 2005 09:54:32)
Copyright (c) 1997-2005 The PHP Group
Zend Engine v2.1.0-dev, Copyright (c) 1998-2005 Zend Technologies
built with ./configure --enable-sockets
exhibits the same behaviour.
Previous Comments:
------------------------------------------------------------------------
[2005-11-08 09:00:26] sniper@php.net
Please try using this CVS snapshot:
http://snaps.php.net/php5-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php5-win32-latest.zip
------------------------------------------------------------------------
[2005-11-08 08:49:34] jelte dot werkhoven at cruisetravel dot nl
...
I expect it to return "ACK", then return " " because of the '\n' and
break the while loop, which it doesn't. As far as I understand from the
manual it should.
------------------------------------------------------------------------
[2005-11-07 15:30:06] sniper@php.net
So what's wrong in this? Of course it's 4 chars.
ACK\n == 4 chars.
------------------------------------------------------------------------
[2005-11-07 09:31:28] jelte dot werkhoven at cruisetravel dot nl
Oh and it doesn't break the while-loop.
------------------------------------------------------------------------
[2005-11-07 09:30:21] jelte dot werkhoven at cruisetravel dot nl
CODE:
echo "Reading daemon response:\n";
while( $out = socket_read($socket, 2048, PHP_NORMAL_READ) ) {
//if( strncmp( $out, 'ACK', 3 ) == 0 ) break;
var_dump( $out );
}
RESULT:
OK got socket.
Attempting to connect to '127.0.0.1' on port '8001'...OK got
connection.
OK wrote connection string 'REQ
'.
Reading daemon response:
string(4) "ACK
"
Note the trailing '\n' to the ACK response, also note it's a string(4).
------------------------------------------------------------------------
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/35086
--
Edit this bug report at http://bugs.php.net/?id=35086&edit=1
Thread (10 messages)