We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
https通讯场景下,使用 webclient_connect 连接成功后, socket fd同时保存在 session->tls_session->server_fd.fd 和 session->socket 中
通讯过程中,如果发生通讯错误, 则会主动调用 closesocket() 关闭通讯socket, 同时只把 session->socket 置为 -1. 此时 session->tls_session->server_fd.fd 中的 fd 号维持不变. (参考 webclient_read / webclient_write 中的错误处理部分)
通讯过程结束时,如果用户直接使用 webclient_clean 清理现场 , 在https使用场景下,会根据 session->tls_session->server_fd.fd 判定socket是否已经关闭,如其值不为 -1 ,则使用closesocket 主动关闭一次,这里在并发场景下,会有socket double close 风险
The text was updated successfully, but these errors were encountered:
No branches or pull requests
https通讯场景下,使用 webclient_connect 连接成功后, socket fd同时保存在
session->tls_session->server_fd.fd 和 session->socket 中
通讯过程中,如果发生通讯错误, 则会主动调用 closesocket() 关闭通讯socket, 同时只把 session->socket 置为 -1.
此时 session->tls_session->server_fd.fd 中的 fd 号维持不变.
(参考 webclient_read / webclient_write 中的错误处理部分)
通讯过程结束时,如果用户直接使用 webclient_clean 清理现场 , 在https使用场景下,会根据 session->tls_session->server_fd.fd
判定socket是否已经关闭,如其值不为 -1 ,则使用closesocket 主动关闭一次,这里在并发场景下,会有socket double close 风险
The text was updated successfully, but these errors were encountered: