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: Tomalak Geret'kal via curl-library <curl-library_at_cool.haxx.se>
Date: Tue, 27 Oct 2020 15:01:05 +0000
On 27/10/2020 14:59, Daniel Stenberg wrote:
> On Tue, 27 Oct 2020, Tomalak Geret'kal via curl-library
> wrote:
>
>> I don't think there's anything to do here in libcurl,
>> beyond confirming (or denying!) that sigpipe_ignore is
>> /supposed/ to be a no-op if neither OpenSSL or Mbed TLS
>> is in use, a fact I discovered while looking into this
>> other issue.
>
> Yes it's on purpose, because it's not needed.
>
> libcurl is designed and meant to prevent signals to get
> sent (if asked to) and it should do that no matter which
> TLS backend it uses.
>
> OpenSSL and mbedTLS provide no way for us to prevent the
> signals from (potentially) being triggered so we must
> ignore them then. Other backends, like the Secure
> Transport one, allow us to not generate any SIGPIPEs, so
> we don't need to add ignore any signals there. It is much
> better to avoid the hassle of ignoring signals.
>
Okay, that's all fine then. Cheers.
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2020-10-27
Date: Tue, 27 Oct 2020 15:01:05 +0000
On 27/10/2020 14:59, Daniel Stenberg wrote:
> On Tue, 27 Oct 2020, Tomalak Geret'kal via curl-library
> wrote:
>
>> I don't think there's anything to do here in libcurl,
>> beyond confirming (or denying!) that sigpipe_ignore is
>> /supposed/ to be a no-op if neither OpenSSL or Mbed TLS
>> is in use, a fact I discovered while looking into this
>> other issue.
>
> Yes it's on purpose, because it's not needed.
>
> libcurl is designed and meant to prevent signals to get
> sent (if asked to) and it should do that no matter which
> TLS backend it uses.
>
> OpenSSL and mbedTLS provide no way for us to prevent the
> signals from (potentially) being triggered so we must
> ignore them then. Other backends, like the Secure
> Transport one, allow us to not generate any SIGPIPEs, so
> we don't need to add ignore any signals there. It is much
> better to avoid the hassle of ignoring signals.
>
Okay, that's all fine then. Cheers.
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2020-10-27