https://bz.apache.org/bugzilla/show_bug.cgi?id=70026
Bug ID: 70026
Summary: RewriteRule documentation outdated and wrong about
AllowOverride (“the rewrite engine cannot be used in
.htaccess files in that directory”)
Product: Apache httpd-2
Version: 2.5-HEAD
Hardware: PC
URL: https://httpd.apache.org/docs/trunk/en/mod/mod_rewrite
.html#rewriterule
Status: NEW
Severity: normal
Priority: P2
Component: Documentation
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
The documentation of the RewriteRule directive contains:
> To enable the rewrite engine in this context, you need to set "RewriteEngine
> On" and the FollowSymLinks or SymLinksIfOwnerMatch Options must be enabled.
> If your administrator has disabled override of these options for a user's
> directory via AllowOverride, the rewrite engine cannot be used in .htaccess
> files in that directory.
This is misleading/confusing due to a few assumptions:
1. That these options can be overriden by default. While this used to be the
case, this is not the case with httpd 2.4+:
https://httpd.apache.org/docs/current/upgrading.html#run-time
2. That the reader has an administrator. Most readers are administrators
themselves. While it was also common 2 or 3 decades ago for administrators to
have administrators themselves with shared hosting, httpd instances which have
multiple groups of administrators (multiple “user directories”) are now a
minority.
3. That distributed configuration files are named “.htaccess”.
"the FollowSymLinks or SymLinksIfOwnerMatch Options must be enabled" is also
poor.
I suggest:
> To enable the rewrite engine in this context, you need to set "RewriteEngine
> On" and at least one of the FollowSymLinks or SymLinksIfOwnerMatch Options
> must be enabled.
🅭🄍: https://www.philippecloutier.com/Common+infrastructure+licensing#its
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
