https://bz.apache.org/bugzilla/show_bug.cgi?id=65627
--- Comment #7 from Ruediger Pluem <rpl...@apache.org> --- (In reply to Yann Ylavic from comment #6) > (In reply to Yann Ylavic from comment #5) > > > > So I think that attachment 38061 [details] is the right thing to do, for > > compatibility. > > The other option is to change mpm_itk to: > - apr_socket_close(ap_get_conn_socket(c)); > - ap_set_core_module_config(c->conn_config, NULL); > + c->aborted = 1; The question is, how we want to allow if at all another module to say that we should get out of the way with regards to lingering closes. Do we allow to set the socket to NULL via ap_set_core_module_config or do we demand that is has to set c->aborted to 1 as you suggest. Depending on this we could modify the proposed patch to either make it an assert that csd != NULL or log an error message in case csd == NULL as this is not expected. If setting the socket to NULL is the accepted way though, the patch proposed here is correct as it is. -- 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
