Daniel Stenberg writes:
> We decided to not copy the debug callback to the close handle since it
> could come as a surprise to application that it could be called even
> after the handle in which it was set had been killed. I fear that
> would be even worse than what we have right now.
Agree.
>
On 5/8/2019 6:27 AM, Kristoffer Gleditsch (kgledits) via curl-library wrote:
> We are using libcurl and multi handles in an application where we want
> debugging output and control over where that output is sent. We do
> this by setting CURLOPT_VERBOSE and CURLOPT_DEBUGFUNCTION, which sends
> all
On Wed, 8 May 2019, Kristoffer Gleditsch (kgledits) via curl-library wrote:
After https://github.com/curl/curl/pull/3618 and
https://github.com/curl/curl/pull/3598, we started getting '* Closing
connection 0' messages on STDERR when curl_multi_cleanup() closes the
connections in the connection
Hi!
We are using libcurl and multi handles in an application where we want
debugging output and control over where that output is sent. We do
this by setting CURLOPT_VERBOSE and CURLOPT_DEBUGFUNCTION, which sends
all the output to our logging code.
After https://github.com/curl/curl/pull/3618 an
