From: Rich Bowen <rbowen@apache.org>
Date: Wed, 29 Apr 2026 20:52:17 +0000 (+0000)
Subject: mod_proxy: Warn about ProxyPassMatch backreference worker matching and connection... 
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=3093fe62ec56c1b303e00b2be07033b3cb24209a;p=thirdparty%2Fapache%2Fhttpd.git

mod_proxy: Warn about ProxyPassMatch backreference worker matching and connection pooling (Bug 62167, related to Bug 43513)

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

diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml
index 6721c8d0a0..979fc0035e 100644
--- a/docs/manual/mod/mod_proxy.xml
+++ b/docs/manual/mod/mod_proxy.xml
@@ -1578,6 +1578,24 @@ when the <var>url</var> parameter contains backreference(s) (see note below).
     <note><strong>Note: </strong>This directive cannot be used within a
     <code>&lt;Directory&gt;</code> context.</note>
 
+    <note type="warning"><title>Worker matching with backreferences</title>
+    <p>When <directive>ProxyPassMatch</directive> contains
+    backreferences (e.g., <code>$1</code>) in the target URL, each
+    request produces a different resolved URL. Because <a
+    href="#workers">workers</a> are matched by URL, these requests
+    will not match the worker created by this directive and will
+    instead use the default reverse proxy worker, which does not
+    reuse connections or cache DNS lookups. To enable connection
+    pooling, define an explicit worker for the backend separately:</p>
+    <highlight language="config">
+ProxyPass        "/notused" "http://backend.example.com/" connectiontimeout=5 timeout=30
+ProxyPassMatch   "^/(.*\.gif)$" "http://backend.example.com/$1"
+    </highlight>
+    <p>The explicit <directive>ProxyPass</directive> worker definition
+    ensures that the backend connection pool is available for use by
+    <directive>ProxyPassMatch</directive> requests.</p>
+    </note>
+
     <p>Suppose the local server has address <code>http://example.com/</code>;
     then</p>