Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
there is a node "node/8" and an alias to this node "web".
when accessing "site.ext/node/8" http response code is 200, but with "site.ext/web" http response code is 404 (but the page is displayed correctly)
if rename the alias to something else (eg: webdesign) the http response code is then correct (200). renaming back to web give back 404.
for the user it's almost invisible but i fear the the search engines.
Comment | File | Size | Author |
---|---|---|---|
#15 | 919596-remove-multiviews.patch | 547 bytes | boombatower |
#7 | multiviews-919596.patch | 673 bytes | dmitrig01 |
#6 | multiviews-919596-6.patch | 653 bytes | AnalogFile |
#2 | web-404.patch | 293 bytes | mathroc |
Comments
Comment #1
Damien Tournoud CreditAttribution: Damien Tournoud commentedThat's probably because of Apache Multiviews feature. We have a file named
web.config
for IIS, and Apache is servingweb
as a shorthand forweb.config
.Can you try adding
Options -Multiviews
to your.htaccess
or your Apache VirtualHost configuration?Comment #2
mathroc CreditAttribution: mathroc commentedthat's it!
serving /web with response 200 :)
Comment #3
AnalogFile CreditAttribution: AnalogFile commentedI do not think this change will be accepted. But I'm too new to Drupal to judge it.
Let's see what others think.
Comment #4
Damien Tournoud CreditAttribution: Damien Tournoud commentedActually, 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.
Comment #6
AnalogFile CreditAttribution: AnalogFile commentedThat patch was too old.
Try this.
Comment #7
dmitrig01 CreditAttribution: dmitrig01 commentedvery slight documentation fix (adding a period at the end, switching the grammar)
Comment #8
Stevel CreditAttribution: Stevel commentedThis doesn't hurt anyone, and makes /web (and any other file-like url alias) work when MultiViews is enabled in the apache config files.
Comment #9
Dries CreditAttribution: Dries commentedCommitted to CVS HEAD. Thanks.
Comment #10
ahaarnos CreditAttribution: ahaarnos commentedThe 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.
Comment #11
amc CreditAttribution: amc commentedComment #12
catchThe need review status is for issues that have active patches to review, that's not the case here.
Comment #13
catchRe-titling.
Comment #14
chx CreditAttribution: chx commentedThere is no mod_negotiate. If you mean mod_negotiation which I presume you do then Apache documentation says that
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.
Comment #15
boombatower CreditAttribution: boombatower commentedThis 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.
Comment #16
boombatower CreditAttribution: boombatower commented- 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.
Comment #17
dawehnerPerhaps it would be good to document this setting in the .htaccess but disable it by default.
Comment #18
dawehnerUpdate status
Comment #19
ahaarnos CreditAttribution: ahaarnos commentedboombatower 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.
Comment #20
boombatower CreditAttribution: boombatower commentedShould probably commit to 8.x and backport?
Comment #21
Dries CreditAttribution: Dries commentedCommitted to 8.x. Moving to 8.x. for webchick to consider.
Comment #22
Damien Tournoud CreditAttribution: Damien Tournoud commentedThis 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?Comment #23
David_Rothstein CreditAttribution: David_Rothstein commentedIt looks like this was actually committed to 7.x already, but not to 8.x:
http://drupalcode.org/project/drupal.git/commit/26d9d42
Comment #24
Dries CreditAttribution: Dries commented@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.