ID: 16261
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Sockets related
Operating System: Linux
PHP Version: 4.0.6
New Comment:
BTW, socket_set_timeout is working fine for me after the socket has
been opened. It's the failure to timeout on the actual fsockopen()
that is causing issues.
Previous Comments:
------------------------------------------------------------------------
[2002-03-25 09:55:46] [EMAIL PROTECTED]
I'm specifying a timeout of 0.2 seconds, but the fsockopen() function
is taking as long as 3-4 seconds with slow domains (I know
www.krasnapolsky.sr to be slow). This example took about 3.6 seconds.
CODE:
echo microtime();
echo fsockopen("www.krasnapolsky.sr", 80, &$errno, &$errstr, 0.2);
echo microtime();
echo "Error Number = $errno, Error String = $errstr";
RESULT:
0.39859300 1016822517
Resource id #1
0.04482100 1016822521
Error Number = 0, Error String =
So the socket is opened -- it just took way longer than I intended to
allow it. Setting the timeout to an integer (e.g. 1) does not work
either (although the documentation says it can be of type float).
I reported this previously under bug 14740, but that thread was related
to win 98 and 2k, where the timeout is not expected to work.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=16261&edit=1
