From: Rich Bowen <rbowen@apache.org>
Date: Fri, 1 May 2026 13:02:44 +0000 (+0000)
Subject: Bug 70015: Clarify FollowSymLinks requirement for per-directory rewrites; note SymLin... 
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=d7f0a425674c7f1f31f0f4140cde4e9d133517db;p=thirdparty%2Fapache%2Fhttpd.git

Bug 70015: Clarify FollowSymLinks requirement for per-directory rewrites; note SymLinksIfOwnerMatch also works

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1933641 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/mod_rewrite.xml b/docs/manual/mod/mod_rewrite.xml
index f0f8cf7ebe..6cd8e76343 100644
--- a/docs/manual/mod/mod_rewrite.xml
+++ b/docs/manual/mod/mod_rewrite.xml
@@ -1143,10 +1143,12 @@ complexity.</li>
 
 <li>To enable the rewrite engine in this context, you need to set
 "<code>RewriteEngine On</code>" <strong>and</strong>
-"<code>Options FollowSymLinks</code>" must be enabled. If your
-administrator has disabled override of <code>FollowSymLinks</code> for
-a user's directory, then you cannot use the rewrite engine. This
-restriction is required for security reasons.</li>
+the <code>FollowSymLinks</code> or <code>SymLinksIfOwnerMatch</code>
+<directive module="core">Options</directive> must be enabled. If your
+administrator has disabled override of these options for a user's
+directory via <directive module="core">AllowOverride</directive>, the
+rewrite engine cannot be used in <code>.htaccess</code> files in that
+directory.</li>
 
 <li>See the <directive module="mod_rewrite">RewriteBase</directive>
 directive for more information regarding what prefix will be added back to