|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2006-11-21 17:16 UTC] tony2001@php.net
[2006-11-21 18:04 UTC] tim at tmcode dot com
[2006-12-02 17:04 UTC] iliaa@php.net
[2006-12-04 23:30 UTC] tim at tmcode dot com
[2006-12-05 01:39 UTC] iliaa@php.net
[2006-12-05 03:12 UTC] tim at tmcode dot com
[2011-09-19 06:34 UTC] simoncpu at gmail dot com
[2011-09-19 08:42 UTC] simoncpu at gmail dot com
|
|||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Mon Oct 27 14:00:01 2025 UTC |
Description: ------------ The 5th parameter of the fsockopen function does not appear to account for a webserver taking too long to complete the ssl/tls handshake. When connecting to an extremely loaded server, the connection might establish within the timeout but the ssl handshake could take much longer. From what I can tell there is no way to set the read/write timeout prior to running fsockopen, making it impossible to prevent PHP from hanging on a slow ssl server? (I tried to find a similar bug or a mention of this issue in the manual so I appologize if I need to go RTFM more carefully). This problem only affects fsockopen if you use ssl:// or tls:// in the first param. If you modifiy the code below and just remove the ssl:// the function call works fine. Reproduce code: --------------- // client code: $fp = fsockopen("ssl://$server", 443, $errno, $errstr, 5); If you want to simulate a "hung" ssl server to verify that the timeout does not happen in 5 seconds: // server code: $sock=socket_create(AF_INET,SOCK_STREAM,SOL_TCP); if(!socket_bind($sock,$serverip,443)) die("bind\n"); if(!socket_listen($sock,25)) die("listen\n"); if(!socket_set_nonblock($sock)) die("nonblock\n"); while(1) { $newfd=@socket_accept($sock); sleep(30); } Expected result: ---------------- fsockopen should timeout after 5 seconds. Actual result: -------------- fsockopen times out after 58 seconds (with the test server code above). Change sleep to something larger and the timeout will take even longer.