Bug #78007 [Opn]: curl_close() does not honor CURLOPT_STDERR

Edit report at https://bugs.php.net/bug.php?id=78007&edit=1 ID: 78007 Updated by: requinix@php.net Reported by: divinity76 at gmail dot com Summary: curl_close() does not honor CURLOPT_STDERR Status: Open Type: Bug Package: cURL related Operating System: Windows 7 x64 SP1 PHP Version: 7.3.5 Block user comment: N Private report: N New Comment: Those messages are indeed coming directly from cURL, not PHP. There's a variety of hardcoded logging statements in it that should, in theory, be controllable by a compile flag and a runtime flag... Previous Comments: ------------------------------------------------------------------------ [2019-05-13 12:26:36] divinity76 at gmail dot com .. i wonder if the libcurl versions here are relevant. cmb@php.net add the libcurl version you're on (php -i | grep -i curl) can NOT reproduce on PHP 7.2.15 on Ubuntu 18.04 x64 kernel 4.15.0, libcurl 7.58.0 CAN reproduce on PHP 7.3.4 on Windows 7 x64 SP1, libcurl 7.64.1 CAN (partially) reproduce on PHP 7.3.5 on Arch Linux x64 kernel 5.0.13, libcurl.. ??? (can't check right now, ill make an update when i can) ------------------------------------------------------------------------ [2019-05-13 11:32:01] cmb@php.net I cannot reproduce this on Windows 10.0.17763.475, neither with PHP 7.3.5 nor with current PHP-7.3 tip. ------------------------------------------------------------------------ [2019-05-13 11:26:16] divinity76 at gmail dot com on PHP 7.3.5 with Arch Linux x64 with kernel 5.0.13 we only get 1 line: * Closing connection 0 - that is better, but still bugged. ------------------------------------------------------------------------ [2019-05-13 10:55:16] divinity76 at gmail dot com .. i forgot to add: CURLOPT_VERBOSE also has to be enabled. it is enabled in the test. ------------------------------------------------------------------------ [2019-05-13 10:49:07] divinity76 at gmail dot com Related To: Bug #77939 ------------------------------------------------------------------------ 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