From: Eric Covener <covener@apache.org>
Date: Sat, 5 Jul 2014 00:06:23 +0000 (+0000)
Subject: xform
X-Git-Tag: 2.5.0-alpha~4003
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=6185eeaccc0f30f37066dedbdf1a450bb2632da0;p=apache

xform


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1607961 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/mod_ldap.html.en b/docs/manual/mod/mod_ldap.html.en
index 979cdac9ab..14c69f8f8a 100644
--- a/docs/manual/mod/mod_ldap.html.en
+++ b/docs/manual/mod/mod_ldap.html.en
@@ -471,13 +471,18 @@ LDAPTrustedGlobalCert CA_BASE64 /certs/cacert2.pem
 
     <p>A setting of 0 causes connections to never be saved in the backend
     connection pool.  The default value of -1, and any other negative value,
-     allows connections of any age to be reused.</p>
+    allows connections of any age to be reused.</p>
 
-    <p>The timemout is based on when the LDAP connection is returned to the
-    pool, not based on the last time I/O has been performed over the backend
-    connection.  If the information is cached, the apparent idle time can exceed
-    the <code class="directive">LDAPConnectionPoolTTL</code>. </p>
+    <p>For performance reasons, the reference time used by this directive is 
+    based on when the LDAP connection is returned to the pool, not the time
+    of the last successful I/O with the LDAP server.  </p>
 
+    <p>Since 2.4.10, new measures are in place to avoid the reference time
+    from being inflated by cache hits or slow requests.  First, the reference
+    time is not updated if no backend LDAP conncetions were needed. Second,
+    the reference time uses the time the HTTP request was received instead
+    of the time the request is completed.</p>
+    
     <div class="note"><p>This timeout defaults to units of seconds, but accepts
     suffixes for milliseconds (ms), minutes (min), and hours (h).
     </p></div>