Buy commercial curl support. 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 Daniel himself.
Re: Does anyone build curl or libcurl without TLS support?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Patrick Monnerat via curl-library <curl-library_at_lists.haxx.se>
Date: Sun, 12 Jan 2025 18:46:42 +0100
On 1/12/25 6:03 PM, Daniel Stenberg wrote:
> On Sun, 12 Jan 2025, Patrick Monnerat via curl-library wrote:
>
>> If you really think it's wasting energy (I think of all
>> conditionals), an alterative would be to implement a dummy backend
>> made of stubs.
>
> That's not gonna work because in such a build curl would assume TLS
> works, but in reality it doesn't. Quite different behavior than today
> without TLS.
Sure, the errors would'nt be reported at the same place(s).
But if the stubs return errors, you'll get them anyway.
This would be a better solution than no libcurl at all !
Date: Sun, 12 Jan 2025 18:46:42 +0100
On 1/12/25 6:03 PM, Daniel Stenberg wrote:
> On Sun, 12 Jan 2025, Patrick Monnerat via curl-library wrote:
>
>> If you really think it's wasting energy (I think of all
>> conditionals), an alterative would be to implement a dummy backend
>> made of stubs.
>
> That's not gonna work because in such a build curl would assume TLS
> works, but in reality it doesn't. Quite different behavior than today
> without TLS.
Sure, the errors would'nt be reported at the same place(s).
But if the stubs return errors, you'll get them anyway.
This would be a better solution than no libcurl at all !
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2025-01-12