#38620 [Fbk]: curl_multi_* - timeout after 4-6 socket connects on different hosts
| From: | tobsn@php.net | Date: | Sat, 02 Sep 2006 18:10:16 +0000 |
| Subject: | #38620 [Fbk]: curl_multi_* - timeout after 4-6 socket connects on different hosts | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-101649@lists.php.net to get a copy of this message | ||
ID: 38620
Updated by: tobsn@php.net
Reported By: tobsn@php.net
Status: Feedback
Bug Type: cURL related
Operating System: Debian Sarge
PHP Version: 5.1.6
New Comment:
see in the manual on the php.net/curl_multi_exec, there is the example
code.
trust me, i tested it very hard with everything i know.
because i need this function... so the only workaround for me is to
code a cpp appl, make a perl script or something else but you cant take
php for this. and this sucks.
because the function is there but you cant use it.
i mean it should work. why is there a function that doesnt work...
drives me nuts ;)
Previous Comments:
------------------------------------------------------------------------
[2006-09-02 17:42:37] mike@php.net
There's no example code on the manual page.
Did you only set the transfer timeout or the connect timeout option
too?
------------------------------------------------------------------------
[2006-09-02 16:31:21] tobsn@php.net
you can set it to 200 seconds, it dont change the result.
------------------------------------------------------------------------
[2006-09-02 16:12:07] mike@php.net
Set a reasonable timeout option then.
------------------------------------------------------------------------
[2006-09-02 14:14:47] tobsn@php.net
because curl_multi is very buggy...
give me an example that it is curl... but i dont think so.
------------------------------------------------------------------------
[2006-09-01 09:37:43] tony2001@php.net
And it's not a problem of cURL because .... ?
------------------------------------------------------------------------
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/38620
--
Edit this bug report at http://bugs.php.net/?id=38620&edit=1