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 <code><Dircectory
+ match a `/' character, so <code><Directory
/*/public_html></code> will not match
<code>/home/user/public_html</code>, but <code><Directory
/home/*/public_html></code> will match. Example:</p>
</Directory><br>
</code></td></tr></table></blockquote>
+<blockquote><table><tr><td bgcolor="#e0e5f5">
+<p>Be careful with the <em>directory-path</em> 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.</p>
+</td></tr></table></blockquote>
+
<p>Extended regular
expressions can also be used, with the addition of the
<code>~</code> character. For example:</p>
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 <code><Dircectory
+ match a `/' character, so <code><Directory
/*/public_html></code> will not match
<code>/home/user/public_html</code>, but <code><Directory
/home/*/public_html></code> will match. Example:</p>
</Directory><br />
</example>
+<note>
+<p>Be careful with the <em>directory-path</em> 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.</p>
+</note>
+
<p>Extended regular
expressions can also be used, with the addition of the
<code>~</code> character. For example:</p>