Why does Antiweb linger on HTTP sockets?
When terminating an HTTP connection with a “Connection: close” HTTP header, Antiweb will shutdown() the write direction of the socket and continue to read and discard data from the socket for up to 2 seconds. This is required for HTTP/1.1 persistent connections. See here for more details. Note that Antiweb’s maximum linger period (2 seconds) is much shorter than Apache’s 30 seconds. Also, we don’t use a SIGALRM. Instead, lingering sockets are tracked with Antiweb’s regular connection state machine. We believe this is correctly implemented but please let us know if you encounter problems.
