Return-Path:
<Dircectory
+ match a `/' character, so
<Directory
/*/public_html>
will not match
/home/user/public_html
, but <Directory
/home/*/public_html>
will match. Example:
+ Be careful with the directory-path arguments: They have +to literally match the filesystem path which Apache uses to access the +files. Directives applied to a particular <Directory> will not +apply to files accessed from that same directory via a different path, +such as via different symbolic links.
+
Extended regular
expressions can also be used, with the addition of the
1.17 +9 -1 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.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- core.xml 14 Jun 2002 11:28:22 -0000 1.16
+++ core.xml 15 Jun 2002 02:48:16 -0000 1.17
@@ -391,7 +391,7 @@
Unix shell-style matching. In a wild-card string, `?' matches any
single character, and `*' matches any sequences of characters.
You may also use `[]' character ranges. None of the wildcards
- match a `/' character, so <Dircectory
+ match a `/' character, so
<Directory
/*/public_html>
will not match
/home/user/public_html
, but <Directory
/home/*/public_html>
will match. Example:
Be careful with the directory-path arguments: They have +to literally match the filesystem path which Apache uses to access the +files. Directives applied to a particular <Directory> will not +apply to files accessed from that same directory via a different path, +such as via different symbolic links.
+Extended regular expressions can also be used, with the addition of the