You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by sl...@apache.org on 2003/04/21 02:24:28 UTC
cvs commit: httpd-2.0/docs/manual/mod core.xml
slive 2003/04/20 17:24:28
Modified: docs/manual/mod core.xml
Log:
Add note about when to use <location>. This dupes what is already discussed
in sections.html, but it is important enough to repeat.
Revision Changes Path
1.59 +19 -5 httpd-2.0/docs/manual/mod/core.xml
Index: core.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/core.xml,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -d -b -u -r1.58 -r1.59
--- core.xml 11 Apr 2003 01:25:51 -0000 1.58
+++ core.xml 21 Apr 2003 00:24:28 -0000 1.59
@@ -1674,10 +1674,24 @@
<code>.htaccess</code> files are read, and after the <directive
type="section" module="core">Files</directive> sections.</p>
- <p>Note that URLs do not have to line up with the filesystem at
- all, it should be emphasized that <directive
- type="section">Location</directive> operates completely
- outside the filesystem.</p>
+ <p><directive type="section">Location</directive> sections operate
+ completely outside the filesystem. This has several consequences.
+ Most importantly, <directive type="section">Location</directive>
+ directives should not be used to control access to filesystem
+ locations. Since several different URLs may map to the same
+ filesystem location, such access controls may by circumvented.</p>
+
+ <note><title>When to use <directive
+ type="section">Location</directive></title>
+
+ <p>Use <directive type="section">Location</directive> to apply
+ directives to content that lives outside the filesystem. For
+ content that lives in the filesystem, use <directive
+ type="section" module="core">Directory</directive> and <directive
+ type="section" module="core">Files</directive>. An exception is
+ <code><Location /></code>, which is an easy way to
+ apply a configuration to the entire server.</p>
+ </note>
<p>For all origin (non-proxy) requests, the URL to be matched is a
URL-path of the form <code>/path/</code>. No scheme, hostname,