https://issues.apache.org/bugzilla/show_bug.cgi?id=50693
Summary: Unexpected behaviour with AllowOverride
Product: Apache httpd-2
Version: 2.2.17
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Core
AssignedTo: [email protected]
ReportedBy: [email protected]
When specifically enabling +SymLinksIfOwnerMatch globally and then disallowing
it from being overridden with AllowOverride, setting +SymLinksIfOwnerMatch in a
.htaccess file causes an internal server error.
This isn't intuitive - setting an option which is already enabled, even if it's
not permitted to be overriden, should not cause an error.
To reproduce, set this globally:
<Directory "/some/directory/path">
Options +All +IncludesNOEXEC -Indexes +SymLinksIfOwnerMatch
AllowOverride All
Options=ExecCGI,Includes,IncludesNOEXEC,Indexes,MultiViews,FollowSymLinks
</Directory>
Then create a .htaccess file in /some/directory/path that contains:
+SymLinksIfOwnerMatch
No override is occurring as the option being set is already set, yet we get an
error. This behaviour causes all default installs of Drupal to give ISE's when
the global configuration is in place.
The purpose of the global configuration, in case it isn't clear, is to enforce
+SymLinksIfOwnerMatch and to cause an ISE if -SymLinksIfOwnerMatch is set in a
.htaccess file.
Thanks,
Vince Stratful.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- 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]
