[Bug 70036] Terms Used to Describe Directives: URL-path definition unclear/misleading

https://bz.apache.org/bugzilla/show_bug.cgi?id=70036

--- Comment #2 from Philippe Cloutier <[email protected]> ---
The main issue also affects Mapping URLs to Filesystem Locations, whose
DocumentRoot section contains:
> In deciding what file to serve for a given request, httpd's default behavior is to take the URL-Path for the request (the part of the URL following the hostname and port) and add it to the end of the DocumentRoot specified in your configuration files.
I recommend:
diff --git a/docs/manual/urlmapping.xml b/docs/manual/urlmapping.xml
--- docs/manual/urlmapping.xml
+++ docs/manual/urlmapping.xml
@@ -71,11 +71,10 @@

 <section id="documentroot"><title>DocumentRoot</title>

     <p>In deciding what file to serve for a given request, httpd's
-    default behavior is to take the URL-Path for the request (the part
-    of the URL following the hostname and port) and add it to the end
-    of the <directive module="core">DocumentRoot</directive> specified
+    default behavior is to take the request’s <a
href="directive-dict.html#Syntax">URL-path</a>
+    and add it to the end of the <directive
module="core">DocumentRoot</directive> specified
     in your configuration files. Therefore, the files and directories
     underneath the <directive module="core">DocumentRoot</directive>
     make up the basic document tree which will be visible from the
     web.</p>


(In reply to Eric Covener from comment #1)
> not worth the churn
Please clarify what you mean

-- 
You are receiving this mail because:
You are the assignee for the bug.