From: Igor Galić <igalic@apache.org>
Date: Thu, 24 Nov 2011 15:34:19 +0000 (+0000)
Subject: Pr#52239: clarify Event MPM's behaviour with strictly
X-Git-Tag: 2.5.0-alpha~7815
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2c7c819a54f1037c062def67cd34800da76aa8c2;p=thirdparty%2Fapache%2Fhttpd.git

Pr#52239: clarify Event MPM's behaviour with strictly
synchronous libraries.


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

diff --git a/docs/manual/misc/security_tips.xml b/docs/manual/misc/security_tips.xml
index 3e91494443f..543b4f65e79 100644
--- a/docs/manual/misc/security_tips.xml
+++ b/docs/manual/misc/security_tips.xml
@@ -117,13 +117,14 @@
 
       <li>The use of a threaded <a href="../mpm.html">mpm</a> may
       allow you to handle more simultaneous connections, thereby
-      mitigating DoS attacks.  Further, the experimental
+      mitigating DoS attacks.  Further, the 
       <module>event</module> mpm
       uses asynchronous processing to avoid devoting a thread to each
-      connection. At the current point of time this
-      is work in progress and not fully implemented.  Especially the
+      connection. Due to the nature of the OpenSSL library the
       <module>event</module> mpm is currently incompatible with
-      <module>mod_ssl</module> and other input filters.</li>
+	  <module>mod_ssl</module> and other input filters. In these
+      cases it falls back to the behaviour of the
+      <module>worker</module> mpm.</li>
 
       <li>There are a number of third-party modules available through
       <a