https://bz.apache.org/bugzilla/show_bug.cgi?id=60956
--- Comment #9 from Frank Meier <frank.me...@ergon.ch> --- Hi Luca, Thanks again, for pushing this forward. Also my understanding of the code is unfortunately not good enough to propose a patch. I completely agree. Either the process of closing should be offloaded to a worker thread, or the function "start_lingering_close_nonblocking" should really guarantee, that it is 'nonblocking' like its name suggests. I slightly favor the path, fixing the start_lingering_close_nonblocking function, but I think this might be more difficult to do. The question is, what should happen if the TLS "close notify" could not be sent. Maybe we could just close the connection uncleanly in this case. It would not be so nice, but on the other hand, at some point you want to get rid of the stalled connection and a 'hard' close might be the only way to achieve that. Cheers -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
