Control: retitle -1 apache2: Please allow htaccess directives forbidden by AllowOverride when they change nothing Control: tags -1 +upstream Control: severity -1 wishlist Hello Vincent On Thursday 29 August 2013 21:08:06 you wrote: > On 2013-08-28 22:43:38 +0000, Jean-Michel Vourgère wrote: > > I believe this is the expected behavior: > > > > I suppose your error.log contains something like : > > "/home/xxx/public_html/.htaccess: Option MultiViews not allowed here" > > > > Tuning Multiview option is forbidden inside an .htaccess unless you explicitly > > allow it. > > But my point is that this rule is too strict because MultiViews was > already enabled in the userdir config file under /etc. > > > This can be fixed by changing: > > AllowOverride FileInfo AuthConfig Limit Indexes > > into > > AllowOverride FileInfo AuthConfig Limit Indexes Options=MultiViews > > IMHO, Options=MultiViews should just mean that the user is allowed > to change the MultiViews status. But if the user doesn't change it, > Options=MultiViews shouldn't be needed. Indeed there's no harm if > the user uses an option that has no effect (because already set > in the same context under /etc). Actually, apache2.4 introduce a new feature: You can ignore forbidden overrides by replacing AllowOverride FileInfo AuthConfig Limit Indexes by AllowOverride FileInfo AuthConfig Limit Indexes Nonfatal=Override This is described at: https://httpd.apache.org/docs/2.4/mod/core.html#allowoverride I know this is not exactly what you ask. Regarding your report, I feel apache is behaving according to its documentation. But this is a possible enhancement indeed.
Attachment:
signature.asc
Description: This is a digitally signed message part.