From: Eric Covener Date: Sun, 22 Jul 2012 14:40:02 +0000 (+0000) Subject: Merge r1364309 from https://svn.apache.org/repos/asf/httpd/httpd/trunk/: X-Git-Tag: 2.4.3~233 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=1049d71d0f2f4995fb69c21f023b7d24d58a8bcd;p=apache Merge r1364309 from https://svn.apache.org/repos/asf/httpd/httpd/trunk/: copy the context restrictions from sections.html for symlink related options git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1364311 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml index 896a5f3d9f..73ea7b30aa 100644 --- a/docs/manual/mod/core.xml +++ b/docs/manual/mod/core.xml @@ -3298,9 +3298,13 @@ directory

Even though the server follows the symlink it does not change the pathname used to match against Directory sections.

-

Note also, that this option gets ignored if set - inside a Location - section.

+ +

The FollowSymLinks and + SymLinksIfOwnerMatch Options work only in Directory sections or + .htaccess files.

+

Omitting this option should not be considered a security restriction, since symlink testing is subject to race conditions that make it circumventable.

@@ -3349,13 +3353,17 @@ directory target file or directory is owned by the same user id as the link. - Note

This option gets ignored if - set inside a Location section.

+ Note +

The FollowSymLinks and + SymLinksIfOwnerMatch Options work only in Directory sections or + .htaccess files.

+

This option should not be considered a security restriction, since symlink testing is subject to race conditions that make it - circumventable.

- + circumventable.

+

Normally, if multiple Options could