cesanta / mongoose

Embedded Web Server
https://mongoose.ws
Other
11.01k stars 2.71k forks source link

Use OPENSSL How to make this connection timeout? to close the mg_connection #2887

Closed gogoxx2024 closed 3 weeks ago

gogoxx2024 commented 3 weeks ago

Environment

line:7523 static void read_conn(struct mg_connection *c)

n is MG_IO_RESET

c->is_tls_hs is 0

if (c->is_tls_hs) mg_tls_handshake(c);

How to make this connection timeout? to close the mg_connection

1 2 3 close the tool 4 5 6

scaprile commented 3 weeks ago

I don't understand what you are doing. Please don't post snapshots, refer to code and attach network captures (files) Please don't mark our code, we already know it, it is yours that we don't know Please correctly describe what you are doing, what is your code, what happens, where, and why Minimum possible to reproduce your issue. Please read https://mongoose.ws/documentation/#best-practices Please see our documentation, and follow the guidelines in our tutorials. When you have that, then we'll reopen this issue if necessary

gogoxx2024 commented 3 weeks ago

What I want to say is that I use SSL HTTP server. When the client connects and communicates, the client closes and the server still has a connection pointer that has not been reclaimed, so it will not be released. What I want to ask is if there is any API that can handle timeouts to release such invalid links

------------------ 原始邮件 ------------------ 发件人: "Sergio R. @.>; 发送时间: 2024年9月7日(星期六) 晚上10:24 收件人: @.>; 抄送: @.>; @.>; 主题: Re: [cesanta/mongoose] Use OPENSSL How to make this connection timeout? to close the mg_connection (Issue #2887)

I don't understand what you are doing. Please don't post snapshots, refer to code and attach network captures (files) Please don't mark our code, we already know it, it is yours that we don't know Please correctly describe what you are doing, what is your code, what happens, where, and why Minimum possible to reproduce your issue. Please read https://mongoose.ws/documentation/#best-practices Please see our documentation, and follow the guidelines in our tutorials. When you have that, then we'll reopen this issue if necessary

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

scaprile commented 3 weeks ago

Please correctly describe what you are doing, what is your code, what happens, where, and why Minimum possible to reproduce your issue. Please read https://mongoose.ws/documentation/#best-practices Please see our documentation, and follow the guidelines in our tutorials. When you have that, then we'll reopen this issue if necessary

gogoxx2024 commented 3 weeks ago

I uploaded my test code to Baidu Cloud Link: https://pan.baidu.com/s/1l8D6Cb1of4PK24E6qpreww   Extraction code: ol6u

HttpDemo. zip is the source code for the vs2015 code project, mongoose master \ tutorials \ http \ http critical server openssl-x64.zip is the ssllib Restclient. zip is a link testing tool for HTTPS Recording. zip demo video

------------------ 原始邮件 ------------------ 发件人: "cesanta/mongoose" @.>; 发送时间: 2024年9月9日(星期一) 凌晨2:13 @.>; @.**@.>; 主题: Re: [cesanta/mongoose] Use OPENSSL How to make this connection timeout? to close the mg_connection (Issue #2887)

Please correctly describe what you are doing, what is your code, what happens, where, and why Minimum possible to reproduce your issue. Please read https://mongoose.ws/documentation/#best-practices Please see our documentation, and follow the guidelines in our tutorials. When you have that, then we'll reopen this issue if necessary

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

scaprile commented 3 weeks ago

If you would have read the tutorials as instructed: https://mongoose.ws/documentation/tutorials/tls/#windows

Windows Only what the example provides in its Makefile is supported

We do not support custom openssl in Windows. Whatever you want to submit to reproduce your issue must be posted here, clear and readable code, and build as standard. As we won't build nor link any third-party library, I will dismiss this.