Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: curl_easy_recv and SIGPIPE
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_cool.haxx.se>
Date: Mon, 26 Oct 2020 23:09:27 +0100 (CET)
On Mon, 26 Oct 2020, Tomalak Geret'kal via curl-library wrote:
> On closer examination, sigpipe_ignore is a no-op unless USE_OPENSSL or
> USE_MBEDTLS are set.
Are you saying you're not using any of them?
> So it seems the call in curl_easy_perform is only really intended to eat up
> pipes raised by either of those libraries, thus perhaps they don't really
> make sense on a "raw" byte-reading function.
Those are the only places that can trigger SIGPIPE, me knowingly! All uses of
the sockets by libcurl itself should already be protected.
Date: Mon, 26 Oct 2020 23:09:27 +0100 (CET)
On Mon, 26 Oct 2020, Tomalak Geret'kal via curl-library wrote:
> On closer examination, sigpipe_ignore is a no-op unless USE_OPENSSL or
> USE_MBEDTLS are set.
Are you saying you're not using any of them?
> So it seems the call in curl_easy_perform is only really intended to eat up
> pipes raised by either of those libraries, thus perhaps they don't really
> make sense on a "raw" byte-reading function.
Those are the only places that can trigger SIGPIPE, me knowingly! All uses of
the sockets by libcurl itself should already be protected.
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://www.wolfssl.com/contact/ ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2020-10-26