svn commit: r1936368 - in httpd/httpd/branches/2.4.x: . docs/manual/mod

Author: jorton
Date: Mon Jul 20 11:47:48 2026
New Revision: 1936368

Log:
Merge r1935589 from trunk:

* docs/manual/mod/mod_proxy.xml: Add clarifications for ProxyRemote and
  <Proxy> containers.

Modified:
   httpd/httpd/branches/2.4.x/   (props changed)
   httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy.xml

Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy.xml
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy.xml	Mon Jul 20 11:42:02 2026	(r1936367)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy.xml	Mon Jul 20 11:47:48 2026	(r1936368)
@@ -505,7 +505,7 @@ ProxyPass "/examples" "http://backend.ex
 
 <usage>
     <p>Directives placed in <directive type="section">Proxy</directive>
-    sections apply only to matching proxied content.  Shell-style wildcards are
+    sections apply only to matching proxied content using a simple string prefix match against the URL.  Shell-style wildcards are also
     allowed.</p>
 
     <p>For example, the following will allow only hosts in
@@ -713,6 +713,13 @@ ProxyRemote "ftp" "http://ftpproxy.mydom
     authentication challenge.  The <a
     href="mod_proxy_http.html#env">Proxy-Chain-Auth</a> environment
     variable has no effect if this argument is used.</p>
+    
+    <note><title>DNS resolution and forward proxies</title>
+    <p>When a forward (remote) proxy is configured, DNS resolution of
+    the origin/backend hostname is only performed on the forward proxy.
+    Any <directive module="mod_proxy">ProxyBlock</directive> rules
+    which restrict access to specific IP addresses must be configured
+    at the forward proxy.</p></note>
 
 </usage>
 </directivesynopsis>