On Wed, 10 Jan 2024, Samuel Henrique via curl-library wrote:
Thank you for the quick response, should I do anything to log this as a
feature request or having this email is enough?
You can create a PR with an added entry in docs/TODO so that it won't be
forgotten and increasing the chances that someone will "grab it" at a later
point.
I have also just started looking into multissl so I understand there might
be more cases where features won't work, if you know about them, I will be
grateful for a heads up (didn't see anything in the docs so far).
I suspect the feature is not used terribly much and when done, only a few
specific combinations so there might be problems lurking we never got
reported.
The other day for example, we got this filed:
https://github.com/curl/curl/issues/12663
... highlighting the fact that we do some setup code paths differently
depending on what TLS libraries configure finds, which may then ultimately
change how a TLS backend works when used in a single setup vs multissl setup.
An interesting challenge.
--
/ daniel.haxx.se
| Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
| https://curl.se/support.html
--
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
