-MultiViews in .htaccess requires odd AllowOverride Options=All,MultiViews

That's probably because of Apache Multiviews feature. We have a file named web.config for IIS, and Apache is serving web as a shorthand for web.config.

Can you try adding Options -Multiviews to your .htaccess or your Apache VirtualHost configuration?

I do not think this change will be accepted. But I'm too new to Drupal to judge it.
Let's see what others think.

Actually, I think it makes sense to disable Multiview by default. We just don't need it in Drupal, and it can make more harm then good.

That patch was too old.
Try this.

very slight documentation fix (adding a period at the end, switching the grammar)

This doesn't hurt anyone, and makes /web (and any other file-like url alias) work when MultiViews is enabled in the apache config files.

Committed to CVS HEAD. Thanks.

The addition of Options -MultiViews to the .htaccess file with the D7 RC1 release is now causing Apache to choke on that line and cause 500 Internal Server Error for my D7 site (none of the other Options -Indexes, etc. lines cause this kind of error).

My server is running Apache with mod_negotiate compiled in, so the multiviews option should be available but for some reason it is not allowed to be adjusted in the .htaccess file.

I suggest this addition be reviewed and further tested, since it can obviously cause problems for some Apache configurations, and this Multiviews/cleanURLs issue has been around as long as I've been using Drupal.

The need review status is for issues that have active patches to review, that's not the case here.

Re-titling.

There is no mod_negotiate. If you mean mod_negotiation which I presume you do then Apache documentation says that

There are two implementations of this.

A type map
A MultiViews search (enabled by the MultiViews Options)

it does not say disabling MultiViews causes havoc, in fact it sounds like it totally should work. If it does not, we need your Apache configuration and version. Also note that we are not getting HTTP 500 bug reports by the hundreds even after release so I am downgrading this.

This breaks it on my default LAMP stack...based on reading the option only works if multiviews is enabled...would highly prefer this was removed...currently patching my d7 installs.

Contrary to what you may think, the All parameter doesn’t really mean “[allow overriding] all options”, since it doesn’t include the MultiViews option! The key here is to use AllowOverride Options=All,MultiViews.

- http://mathiasbynens.be/notes/apache-allowoverride-all

The above fixed the problem for me...I had been just applying this patch, but gets old real fast after setting up a number of instances.

Having such an a-typical configuration requirement is just silly. Based on some other comments it sounds like this only occurs on Apache 2.2 and later which could be the reason we haven't gotten many reports. I don't know what generally is the accepted version, but seems new enough that plenty of hosts may not use it...

Either way can we please get rid of this.

Perhaps it would be good to document this setting in the .htaccess but disable it by default.

Update status

boombatower is exactly right about the Apache config issue (http://drupal.org/node/919596#comment-4061664). We don't have MultiViews enabled in my organization's Apache configurations anyways, but since AllowOverride ALL doesn't include MultiViews (which is stated all over the Apache 2.2 documentation), trying to disable it via .htaccess leads to 500 errors if you're not allowed to override that setting.

I haven't found any sort of conditional way to set an Apache option in .htaccess ONLY IF you have the right to, so I'd consider any default .htaccess that tries to change a setting specifically excluded from the All options set in Apache to be a bad idea.

Should probably commit to 8.x and backport?

Committed to 8.x. Moving to 8.x. for webchick to consider.

This is very weird. Why is this happening only to some people? None of our test bots have this issue, and I never seen AllowOverride All not sufficient to disable multiview. Maybe it only work silently when the multiview is not already on, ie. when the directive actually has no effect?

It looks like this was actually committed to 7.x already, but not to 8.x:
http://drupalcode.org/project/drupal.git/commit/26d9d42

@DamZ: yeah, it's weird but apparently it fixes the problem, and keeps the tests bots happy.

@David: thanks for catching that -- I don't know how you do it ... :) Committed the patch to 8.x too.