Mailing-List: contact cvs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r1819323 - /httpd/httpd/trunk/docs/manual/mod/event.html.en
Date: Wed, 27 Dec 2017 09:27:08 -0000
To: cvs@httpd.apache.org
From: elukey@apache.org
Message-Id: <20171227092708.64ABC3A0316@svn01-us-west.apache.org>
archived-at: Wed, 27 Dec 2017 09:27:10 -0000

Author: elukey
Date: Wed Dec 27 09:27:08 2017
New Revision: 1819323

URL: http://svn.apache.org/viewvc?rev=1819323&view=rev
Log:
event documentation rebuild

Modified:
    httpd/httpd/trunk/docs/manual/mod/event.html.en

Modified: httpd/httpd/trunk/docs/manual/mod/event.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/event.html.en?rev=1819323&r1=1819322&r2=1819323&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/event.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/event.html.en Wed Dec 27 09:27:08 2017
@@ -136,7 +136,9 @@ of the <code class="directive">AsyncRequ
             sockets and they can be re-used to serve other requests.</dd>
 
             <dt>Closing</dt>
-            <dd>Sometimes the MPM needs to perform a lingering close, namely sending back an early error to the client while it is still transmitting data to httpd. Sending the response and then closing the connection immediately is not the correct thing to do since the client (still trying to send the rest of the request) would get a connection reset and could not read the httpd's response. So in such cases, httpd tries to read the rest of the request to allow the client to consume the response. The lingering close is time bounded but it can take relatively long time, so a worker thread can offload this work to the listener.</dd>
+            <dd>Sometimes the MPM needs to perform a lingering close, namely sending back an early error to the client while it is still transmitting data to httpd. Sending the response and then closing the connection immediately is not the correct thing to do since the client (still trying to send the rest of the request) would get a connection reset and could not read the httpd's response. So in such cases, httpd tries to read the rest of the request to allow the client to consume the response. The lingering close is time bounded but it can take relatively long time, so a worker thread can offload this work to the listener. From 2.4.28 onward
+            the listener does not perform the lingering close anymore but it offloads the job to the first worker available.
+            </dd>
         </dl>
 
         <p>These improvements are valid for both HTTP/HTTPS connections.</p>