<p>Even though the server follows the symlink it does <em>not</em>
change the pathname used to match against <codeclass="directive"><ahref="#directory"><Directory></a></code> sections.</p>
<p>Note also, that this option <strong>gets ignored</strong> if set
inside a <codeclass="directive"><ahref="#location"><Location></a></code>
section.</p>
<p>The <code>FollowSymLinks</code> and
<code>SymLinksIfOwnerMatch</code><codeclass="directive"><ahref="#options">Options</a></code> work only in <codeclass="directive"><ahref="#directory"><Directory></a></code> sections or
<code>.htaccess</code> files.</p>
<p>Omitting this option should not be considered a security restriction,
since symlink testing is subject to race conditions that make it
circumventable.</p>
@@ -2531,12 +2533,15 @@ directory</td></tr>
target file or directory is owned by the same user id as the
link.
<divclass="note"><h3>Note</h3><p>This option gets ignored if
set inside a <codeclass="directive"><ahref="#location"><Location></a></code> section.</p>
<divclass="note"><h3>Note</h3>
<p>The <code>FollowSymLinks</code> and
<code>SymLinksIfOwnerMatch</code><codeclass="directive"><ahref="#options">Options</a></code> work only in <codeclass="directive"><ahref="#directory"><Directory></a></code> sections or
<code>.htaccess</code> files.</p>
<p>This option should not be considered a security restriction,
since symlink testing is subject to race conditions that make it
circumventable.</p></div>
</dd>
circumventable.</p>
</div></dd>
</dl>
<p>Normally, if multiple <codeclass="directive">Options</code> could