From 8758b2ab056046e951b04ca293c1f4fbcefa4b31 Mon Sep 17 00:00:00 2001
From: Ruediger Pluem <rpluem@apache.org>
Date: Tue, 11 Apr 2023 12:04:01 +0000
Subject: * Clarify performance topic

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1909067 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/rewrite/flags.xml | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

(limited to 'docs')

diff --git a/docs/manual/rewrite/flags.xml b/docs/manual/rewrite/flags.xml
index 13152a42ed..ea8b0ce3ad 100644
--- a/docs/manual/rewrite/flags.xml
+++ b/docs/manual/rewrite/flags.xml
@@ -597,11 +597,17 @@ client undue influence.</p>
 
 <note type="warning">
 <title>Performance warning</title>
-<p>Using this flag triggers the use of <module>mod_proxy</module>, without handling of persistent connections. This
-means the performance of your proxy will be better if you set it up with <directive module="mod_proxy">ProxyPass</directive> or
-<directive module="mod_proxy">ProxyPassMatch</directive></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>
+<p>Using this flag triggers the use of <module>mod_proxy</module>, without
+handling of persistent connections as the default worker is used in this case,
+which does not handle connection pooling/reuse.</p>
+<p>In order to use persistent connections you need to setup a
+<directive module="mod_proxy">Proxy</directive> block at least for the scheme
+and host part of the target URL containing a
+<directive module="mod_proxy">ProxySet</directive> directive where you e.g. set
+a timeout.</p>
+<p>If you set it up with <directive module="mod_proxy">ProxyPass</directive> or
+<directive module="mod_proxy">ProxyPassMatch</directive> persistent connections
+will be used automatically.</p>
 </note>
 
 <p>Note: <module>mod_proxy</module> must be enabled in order
-- 
cgit v1.2.1