This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
When you tell someone a URL, he often habitually adds a trailing slash as on most websites: http://docs.webplatform.org/wiki/tutorials/device_orientation/ This results in an empty new-page UI. Suggest configuring server to redirect.
Personally I think it's not an issue, I don't know anyone who does that. Nonetheless I guess it would be possible to set up in Apache.
It is just a UX issue for those that add a trailing slash. I don't think it affects many people. Nonetheless it can be done in apache using some rules [1]. [1] http://stackoverflow.com/questions/3082825/mod-rewrite-remove-trailing-slash-only-one
I assume there's also a marginal chance someone might casually navigate to "page/", see there's no content there, then create the page even though content already exists at "page".
I don't see any reason to go through the trouble of making a page dynamically with the content that is supposed to be there when we can do a simple .htaccess rule to get people to the right page.
*** Bug 20865 has been marked as a duplicate of this bug. ***
In bug 20865 Doug pointed out what should be the proper rewrite rule to add to the .htaccess file. That is: RedirectMatch permanent ^/wiki/(.*)/$ /wiki/$1
Nice tagging Garbee, had already forgotten about this one. :) Regex looks reasonable. I was just pondering if there are any (special) pages that require a trailing slash in certain cases, but couldn't think of any. Permanent is OK, too, as we don't want to have content under the trailing-slash-URL later anyways. So, LGTM.
The redirect has been added to all 5 applications servers. Thanks Garbee!