summaryrefslogtreecommitdiffstats
path: root/docs/manual/rewrite/flags.html.en
diff options
context:
space:
mode:
authorLuca Toscano <elukey@apache.org>2017-07-27 14:30:20 +0200
committerLuca Toscano <elukey@apache.org>2017-07-27 14:30:20 +0200
commit579e1799fbaef8bf32e4b202c8388a0fbe043120 (patch)
tree2865665bb50b1ee1724373ee4339edce32b882a1 /docs/manual/rewrite/flags.html.en
parentevent: Avoid possible blocking in the listener thread when shutting down (diff)
downloadapache2-579e1799fbaef8bf32e4b202c8388a0fbe043120.tar.xz
apache2-579e1799fbaef8bf32e4b202c8388a0fbe043120.zip
Clarify some mod_proxy concepts in the docs
I have recently got some basic mod-proxy concepts and these simple info would have helped me a lot: - connection pooling == reuse. My brain did not pick up this simple nomenclature at first read for some reason, probably because we have parameters called "*reuse*" and not "*pooling*". I find the term "reuse" clearer than "pooling", but this is debatable :) - the concept of "Worker" needs to be read before the ProxyPass section (that people probably read directly after checking a search engine) to fully understand its power. - the fact that a worker is related to a single process (and not shared as a Balancer) is a really important concept that I tried to highlight when talking about maxconns (question popped up a lot of times from users). Hope that my understanding is correct, feedback is welcome. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1803171 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual/rewrite/flags.html.en')
-rw-r--r--docs/manual/rewrite/flags.html.en2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/manual/rewrite/flags.html.en b/docs/manual/rewrite/flags.html.en
index d2621ba7c4..722e6462c9 100644
--- a/docs/manual/rewrite/flags.html.en
+++ b/docs/manual/rewrite/flags.html.en
@@ -536,7 +536,7 @@ client undue influence.</p>
<p>Using this flag triggers the use of <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>, without handling of persistent connections. This
means the performance of your proxy will be better if you set it up with <code class="directive"><a href="../mod/mod_proxy.html#proxypass">ProxyPass</a></code> or
<code class="directive"><a href="../mod/mod_proxy.html#proxypassmatch">ProxyPassMatch</a></code></p>
-<p>This is because this flag triggers the use of the default worker, which does not handle connection pooling.</p>
+<p>This is because this flag triggers the use of the default worker, which does not handle connection pooling/reuse.</p>
<p>Avoid using this flag and prefer those directives, whenever you can.</p>
</div>