Bug #78007 [Fbk->Nab]: curl_close() does not honor CURLOPT_STDERR

Edit report at https://bugs.php.net/bug.php?id=78007&edit=1 ID: 78007 Updated by: cmb@php.net Reported by: divinity76 at gmail dot com Summary: curl_close() does not honor CURLOPT_STDERR -Status: Feedback +Status: Not a bug Type: Bug Package: cURL related Operating System: Windows 7 x64 SP1 PHP Version: 7.3.5 -Assigned To: +Assigned To: cmb Block user comment: N Private report: N New Comment: So this is not a PHP bug. Previous Comments: ------------------------------------------------------------------------ [2019-06-06 09:15:46] divinity76 at gmail dot com @mike indeed, can not reproduce on PHP 7.3.4 with libcurl 7.65.0 :) ------------------------------------------------------------------------ [2019-06-06 08:08:34] mike@php.net Should be fix in upstream libcurl 7.65 ------------------------------------------------------------------------ [2019-05-13 20:14:13] divinity76 at gmail dot com a PHP userland workaround, run this before calling curl_close: <?php if(true){ // workaround for https://bugs.php.net/bug.php?id=78007 curl_setopt_array( $ch, array(CURLOPT_VERBOSE=>0,CURLOPT_URL=>null)); curl_exec($ch); } curl_close ( $ch ); ?> .. exactly why i have to call curl_exec(), why it doesn't just work to just set CURLOPT_VERBOSE to 0, i don't know. ------------------------------------------------------------------------ [2019-05-13 15:35:34] cmb@php.net Indeed, if I apply commit d51c7d6[1] on top of libcurl 7.64.1, no more spurious output appears. So I don't think there's anything wrong here on the PHP side. [1] <https://github.com/curl/curl/pull/3856/commits/d51c7d63e7e850980553729b4c366f4377308bba> ------------------------------------------------------------------------ [2019-05-13 13:45:40] divinity76 at gmail dot com Daniel Stenberg (the libcurl author) says it's probably related to https://curl.haxx.se/mail/lib-2019-05/0021.html ------------------------------------------------------------------------ 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=78007 -- Edit this bug report at https://bugs.php.net/bug.php?id=78007&edit=1