You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2004/10/19 19:26:47 UTC
DO NOT REPLY [Bug 31782] New: -
AllowOverride limitations can be overcome w/ Location directive, a note to that effect in the docs would be nice.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31782>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31782
AllowOverride limitations can be overcome w/ Location directive, a note to that effect in the docs would be nice.
Summary: AllowOverride limitations can be overcome w/ Location
directive, a note to that effect in the docs would be
nice.
Product: Apache httpd-2.0
Version: 2.0-HEAD
Platform: All
URL: http://httpd.apache.org/docs-
2.0/mod/core.html#allowoverride
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: Documentation
AssignedTo: bugs@httpd.apache.org
ReportedBy: ferguson@berbee.com
The allowoverride categories are sometimes too general. For instance, you may
want to let webmasters override some of the Options category, but not all of it.
Most often, you might want to restrict ExecCGI or Includes, but otherwise, give
controll to the webmaster. This can be done with the following:
<Directory />
AllowOverride All
</Directory>
<Location />
Options +IncludesNoEXEC -ExecCGI
</Location>
Since Location supercedes Directory and htaccess settings, this effectively
gives control of a subset of the Options category to htaccess users. I think
this is a fairly common thing to want to do, so making a note of it somewhere in
the documentation would be a nice addition.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org