Bug #78404 [Opn]: Curl Multi Handle: curl_error($ch) returns no error string

Edit report at https://bugs.php.net/bug.php?id=78404&edit=1 ID: 78404 User updated by: sa dot su dot technic at gmail dot com Reported by: sa dot su dot technic at gmail dot com Summary: Curl Multi Handle: curl_error($ch) returns no error string Status: Open Type: Bug Package: cURL related Operating System: Debian 8 PHP Version: 7.3.8 Block user comment: N Private report: N New Comment: I am a newbie to this php bug reports. Is it correct that a fix will be released with version 7.2.22? Will there be a fix for 7.3, too? Thank you very much for your effort. Previous Comments: ------------------------------------------------------------------------ [2019-08-12 12:08:19] sa dot su dot technic at gmail dot com But for php version 7.2.15 and previous it worked fine and outputs an error message. So I have to accept that to be that way? ------------------------------------------------------------------------ [2019-08-12 11:59:33] nikic@php.net This looks related to bug #77946. ------------------------------------------------------------------------ [2019-08-12 11:18:10] sa dot su dot technic at gmail dot com Is it possible that it does not work as expected because of curl version 7.38.0 ? I can see that the package php7.3-curl depends on "libcurl4" and I only have "libcurl3"? I can not update that because of debian 8. ------------------------------------------------------------------------ [2019-08-12 10:49:56] sa dot su dot technic at gmail dot com I use "curl 7.38.0 (x86_64-pc-linux-gnu) libcurl/7.38.0 OpenSSL/1.0.1t zlib/1.2.8 libidn/1.29 libssh2/1.4.3 librtmp/2.3" There is no change to the version I used with php 7.2 and there everything works as expected. ------------------------------------------------------------------------ [2019-08-12 09:37:31] requinix@php.net What version of cURL are you using? Because this looks like an upstream matter. Between 7.58 and 7.64 (the two versions I have on hand) two things changed: 1. Errors during multi operations "bubble up" into the original handles 2. Port number error message was removed https://github.com/curl/curl/commit/46e1640#diff-8fb104c402dc51bdffef05a372f32aa2L3447 I modified your example to set CURLOPT_VERBOSE and mark the two messages with 1/2. On 7.64 on Windows I get * Expire in 0 ms for 6 (transfer 0x20d4a2f41c0) * Expire in 0 ms for 6 (transfer 0x20d4a2f9980) * Protocol "foobar" not supported or disabled in libcurl * Closing connection -1 * Closing connection -1 1: Protocol "foobar" not supported or disabled in libcurl 2: With 7.58 on Ubuntu 18.04 I get * Protocol "Foobar" not supported or disabled in libcurl * Closing connection -1 * Port number out of range * Closing connection -1 1: 2: ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=78404 -- Edit this bug report at https://bugs.php.net/bug.php?id=78404&edit=1