Clarify <Location> behavior with forward vs reverse proxy (closes #54309)

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

diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml
index 74084176ade66916a665986d5d088ec40d9f975e..c11faa97df1df85519358f5b95e45f03d02296e6 100644 (file)
--- a/docs/manual/mod/core.xml
+++ b/docs/manual/mod/core.xml
@@ -3161,9 +3161,16 @@ URLs</description>
     <p>For all origin (non-proxy) requests, the URL to be matched is a
     URL-path of the form <code>/path/</code>.  <em>No scheme, hostname,
     port, or query string may be included.</em>  For proxy requests, the
-    URL to be matched is of the form
+    URL to be matched depends on the type of proxy. With a
+    <strong>forward</strong> proxy (<directive
+    module="mod_proxy">ProxyRequests</directive>), the URL to be
+    matched is of the form
     <code>scheme://servername/path</code>, and you must include the
-    prefix.</p>
+    prefix. With a <strong>reverse</strong> proxy (configured via
+    <directive module="mod_proxy">ProxyPass</directive> or
+    <directive module="mod_proxy">RewriteRule ... [P]</directive>),
+    the request arrives as a local URL-path, so use <code>/path/</code>
+    just as you would for origin requests.</p>
 
     <p>The URL may use wildcards. In a wild-card string, <code>?</code> matches
     any single character, and <code>*</code> matches any sequences of