Lighttpd

A remote client may be unprepared for such a shutdown, because lighttpd did not include a "Connection: close" header in its reply and attempt a second request on the same connection.

That is a bug, but not in lighttpd.

This ticket is a feature request.

The patch as provided is too blunt. As noted, it may result in premature closure of keep-alive connections when server.stream-request-body = 1 is in use and the backend has not yet read the full request body.

The following might be a better solution, since it will trigger "Connection: close" if the response body has not been fully read and one of: there is no backend which might be streaming the request body or there is no streaming request body. The short-circuit to check for any content length in the patch below is because many requests are GET requests without a request body.

     /* disable keep-alive if requested */
     if (con->request_count > con->conf.max_keep_alive_requests || 0 == con->conf.max_keep_alive_idle) {
         con->keep_alive = 0;
+    } else if (0 != con->request.content_length
+               && con->request.content_length != con->request_content_queue->bytes_in
+               && (con->mode == DIRECT || 0 == con->conf.stream_request_body)) {
+        con->keep_alive = 0;
     } else {
         con->keep_alive_idle = con->conf.max_keep_alive_idle;
     }

Applied in changeset 629b16f188173b1d4d7434fc68fb85938b2fc582.