Hello everyone, I just took a look at this bug report by Jean-Francois and think that this is rather an issue with libcurl’s SSL/TLS session handling. In my opinion the SSL/TLS sessions should not be freed before all SSL/TLS connections using it are fully closed down. What does everyone else think about this? Another alternative to the workaround provided by Jean-Francois would be to mark the session as not being cached any longer. In that case the reference counter would be decremented and finally the session would be freed during individual connection shutdown. This would also align to the current approach that the SChannel code uses to setup a new session if the old one is stale. The stale session is deleted from the cache and the new one is put into it, while the stale session might still be used for active connections. See the following lines: Jean-Francois, would you mind trying the attached patch as an alternative workaround? Thanks in advance. |
0001-curl_schannel.c-mark-session-as-removed-from-cache-i.patch
Description: Binary data
Best regards, Marc
|
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
