Bug 69092: Expand Location examples to clarify non-filesystem use (proxy, access...

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

diff --git a/docs/manual/sections.xml b/docs/manual/sections.xml
index e2974aa3a013116581d51c8edd873aaff3e4eef2..d7bd32afa9f6b2209aafa129acbd8bdde49f707f 100644 (file)
--- a/docs/manual/sections.xml
+++ b/docs/manual/sections.xml
@@ -223,15 +223,31 @@ as any other requests starting with the <code>/private</code> string.</p>
 <p>The <directive type="section" module="core">Location</directive>
 directive need not have anything to do with the filesystem.
 For example, the following example shows how to map a particular
-URL to an internal Apache HTTP Server handler provided by <module>mod_status</module>.
-No file called <code>server-status</code> needs to exist in the
+URL to an internal handler provided by <module>mod_status</module>.
+No file called <code>server-status</code> needs to exist on the
 filesystem.</p>
 
 <highlight language="config">
+# Map a URL to a built-in handler:
 &lt;Location "/server-status"&gt;
     SetHandler server-status
 &lt;/Location&gt;
+
+# Map a URL path to a reverse proxy backend:
+&lt;Location "/app"&gt;
+    ProxyPass "http://backend.example.com/"
+    ProxyPassReverse "http://backend.example.com/"
+&lt;/Location&gt;
+
+# Deny access to a URL path regardless of what serves it:
+&lt;Location "/private"&gt;
+    Require all denied
+&lt;/Location&gt;
 </highlight>
+
+<p>Because <directive type="section" module="core">Location</directive>
+operates on URLs rather than filesystem paths, it is the appropriate
+container for proxy configuration and module-provided endpoints.</p>
 </section>
 
 <section id="overlapping-webspace"><title>Overlapping Webspace</title>