]> git.ipfire.org Git - thirdparty/apache/httpd.git/commitdiff
mod_proxy: clarify ProxyPass ordering in Location blocks (bz#60479)
authorRich Bowen <rbowen@apache.org>
Thu, 30 Apr 2026 14:46:38 +0000 (14:46 +0000)
committerRich Bowen <rbowen@apache.org>
Thu, 30 Apr 2026 14:46:38 +0000 (14:46 +0000)
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1933602 13f79535-47bb-0310-9956-ffa450edef68

docs/manual/mod/mod_proxy.xml

index 979fc0035ead27d9617fb2674d1c99145eca3adf..8ff5db75977c45ecf21ff9002a3dfab34cbf6905 100644 (file)
@@ -1039,8 +1039,15 @@ ProxyPass "/mirror/foo/i" "!"
     <note type="warning"><title>Ordering ProxyPass Directives in Locations</title>
       <p>Only one <directive module="mod_proxy">ProxyPass</directive> directive
       can be placed in a <directive module="core">Location</directive> block,
-      and the most specific location will take precedence.</p>
+      and the last matching
+      <directive module="core">Location</directive> block takes precedence,
+      following the standard
+      <a href="../sections.html#merging">section merging</a> rules.
+      Place more-specific <directive module="core">Location</directive>
+      blocks <em>after</em> less-specific ones to ensure the intended
+      <directive module="mod_proxy">ProxyPass</directive> applies.</p>
     </note>
+
     <note type="warning"><title>Exclusions and the no-proxy environment variable</title>
       <p>Exclusions must come <em>before</em> the
       general <directive>ProxyPass</directive> directives. In 2.4.26 and later, the "no-proxy"