On Thu, Jul 05, 2018 at 06:40:10PM -0600, Philip Prindeville wrote:
> http://www.wangafu.net/~nickm/libevent-book/Ref6a_advanced_bufferevents.html
>
> "Currently the only workaround is to do lazy SSL shutdowns manually. While
> this breaks the TLS RFC, it will make sure that sessions will stay in cache
> once closed. The following code implements this workaround.”
>
> Is this still the case? I was hoping that libevent had gotten updated and
> the book was lagging behind...
Looks like it is, since there is no SSL_shutdown() around.
AFAIR I tried to add it, but it is not that simple since SSL_shutdown()
generates IO ("close notify"), while once we are ready to close the
socket we are not expecting this.
***********************************************************************
To unsubscribe, send an e-mail to [email protected] with
unsubscribe libevent-users in the body.
