PR55352: mention in the <Proxy> manual that the matching is a prefix only, not

the same context-root / segment-aware matching done by <Location>.

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

diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml
index 08afa84d33cc295960a23bbb119013253bf84f3f..5faed40375e44d35d7ba599d26a3666a04703ff5 100644 (file)
--- a/docs/manual/mod/mod_proxy.xml
+++ b/docs/manual/mod/mod_proxy.xml
@@ -464,6 +464,20 @@ ProxyPass /examples http://backend.example.com/examples timeout=10
 </Proxy>
     </highlight>
 
+    <note><title>Differences from the Location configuration section</title>
+      <p>A backend URL matches the configuration section if it begins with the 
+      the <var>wildcard-url</var> string, even if the last path segment in the
+      directive only matches a prefix of the backend URL.  For example, 
+      &lt;Proxy http://example.com/foo&gt; matches all of 
+      http://example.com/foo, http://example.com/foo/bar, and 
+      http://example.com/foobar.  The matching of the final URL differs
+      from the behavior of the <directive type="section" module="core"
+      >Location</directive> section, which for purposes of this note 
+      treats the final path component as if it ended in a slash.</p>
+      <p>For more control over the matching, see <directive type="section"
+      >ProxyMatch</directive>.</p>
+    </note>
+
 </usage>
 <seealso><directive type="section" module="mod_proxy">ProxyMatch</directive></seealso>
 </directivesynopsis>