From: Rich Bowen <rbowen@apache.org>
Date: Fri, 1 May 2026 13:15:47 +0000 (+0000)
Subject: Bug 64900: Document that path/regex is required for ProxyPass, ProxyPassMatch, ProxyP... 
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=4c21f8da5b821e134d47c148c8e364bdc7c887ae;p=thirdparty%2Fapache%2Fhttpd.git

Bug 64900: Document that path/regex is required for ProxyPass, ProxyPassMatch, ProxyPassReverse outside Location

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

diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml
index 8ff5db7597..c6884701a9 100644
--- a/docs/manual/mod/mod_proxy.xml
+++ b/docs/manual/mod/mod_proxy.xml
@@ -953,7 +953,10 @@ expressions</description>
     <p>When used inside a <directive type="section" module="core"
     >Location</directive> section, the first argument is omitted and the local
     directory is obtained from the <directive type="section" module="core"
-    >Location</directive>. The same will occur inside a
+    >Location</directive>. When used outside a <directive type="section"
+    module="core">Location</directive> or <directive type="section"
+    module="core">LocationMatch</directive> section, the
+    <var>path</var> argument is required. The same will occur inside a
     <directive type="section" module="core">LocationMatch</directive> section;
     however, ProxyPass does not interpret the regexp as such, so it is necessary
     to use <directive>ProxyPassMatch</directive> in this situation instead.</p>
@@ -1620,7 +1623,10 @@ ProxyPassMatch "^/(.*\.gif)$" "http://backend.example.com/$1"
     <p>When used inside a <directive type="section" module="core"
     >LocationMatch</directive> section, the first argument is omitted and the
     regexp is obtained from the <directive type="section" module="core"
-    >LocationMatch</directive>.</p>
+    >LocationMatch</directive>. When used outside a <directive type="section"
+    module="core">Location</directive> or <directive type="section"
+    module="core">LocationMatch</directive> section, the
+    <var>regex</var> argument is required.</p>
 
     <p>If you require a more flexible reverse-proxy configuration, see the
     <directive module="mod_rewrite">RewriteRule</directive> directive with the
@@ -1741,7 +1747,10 @@ ProxyPassReverseCookiePath  "/"  "/mirror/foo/"
     <p>When used inside a <directive type="section" module="core"
     >Location</directive> section, the first argument is omitted and the local
     directory is obtained from the <directive type="section" module="core"
-    >Location</directive>. The same occurs inside a <directive type="section"
+    >Location</directive>. When used outside a <directive type="section"
+    module="core">Location</directive> or <directive type="section"
+    module="core">LocationMatch</directive> section, the
+    <var>path</var> argument is required. The same occurs inside a <directive type="section"
     module="core">LocationMatch</directive> section, but will probably not work as
     intended, as ProxyPassReverse will interpret the regexp literally as a
     path; if needed in this situation, specify the ProxyPassReverse outside