You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by jo...@apache.org on 2026/06/23 15:42:18 UTC

svn commit: r1935589 - httpd/httpd/trunk/docs/manual/mod

Author: jorton
Date: Tue Jun 23 15:42:18 2026
New Revision: 1935589

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

Modified:
   httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml

Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml	Tue Jun 23 14:58:20 2026	(r1935588)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml	Tue Jun 23 15:42:18 2026	(r1935589)
@@ -514,7 +514,7 @@ ProxyPass "/apps"     "http://127"
 
 <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
@@ -734,6 +734,13 @@ ProxyRemote ftp http://ftpproxy.mydomain
     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>