lazy404 at gmail
May 11, 2008, 1:49 PM
Post #1 of 1
(26 views)
Permalink
|
|
AllowOverride Options vs AllowOverride Options= reloaded
|
|
Hello to all,
in https://issues.apache.org/bugzilla/show_bug.cgi?id=44262 I was told
to ask about this issue on dev[at]httpd.apache.org.
Long talk short (i gues my last mail was to long to be comprehensible ;)
In apache 1.3/2.0 there was no selection of whitch options can or
can't be set in .htacess files.
At some point in 2.2.x AllowOverride Options=[option1,...] was introduced.
From my point needlessly it brakes compatibility previous apache
versions, because now AllowOverride Options only allows to set *'All'
options whith isn't really all
because 'All' laves out OPT_INCNOEXEC OPT_SYM_OWNER OPT_MULTI !,
AllowOverride All allows these 3 extra options just as 'AllowOverride
Options=' whitch should be a syntax error but leaves overridable
options unaltered and defaults overridables (from the same patch) are
OPT_ALL + OPT_INCNOEXEC + OPT_SYM_OWNER OPT_MULTI.
*) 'All' like All in Options All whitch really isn't all options
AllowOverride | 1.3/20 | 2.2.x
-----------------------+-------------------------------------------------------
Options | All + Multiviews and 2 others | only All
Options= | n/a | All
+ Multiviews and 2 others
If it's designed to work this way there should be something in the
docs but then what does Options= mean ?
--
Michał Grzędzicki
|
