https://issues.apache.org/bugzilla/show_bug.cgi?id=41270
--- Comment #15 from Yann Ylavic <[email protected]> --- (In reply to harm from comment #14) > I cannot believe Apache ships with TCP_DEFER_ACCEPT on 1 sec, or even > enabled at all. This isn't the case anymore, the new value is 30s since 2.2.28 (and has always been 30s in 2.4.x), still hardcoded though. By the way, TCP_DEFER_ACCEPT=1 is not really a second since TCP_SYNCNT (defaulting to sysctl's tcp_synack_retries when the option is not set like in httpd) is always honored (the final client's 3Way handshake ACK being continuously dropped during defer-accept, there is no real SYN/ACK to send after the one already sent for the SYN, so I mean the time that would have been needed by the server to send that many ACKs). Consequently, one can also play with net.ipv4.tcp_synack_retries (or TCP_SYNCNT) to adjust the TCP_DEFER_ACCEPT timeout as needed (above 30s). > I don't see the possible gain to have this feature enabled. Well, the listener won't accept (spend resources for) spurious connections, which stay in kernel land. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
