Last modified: 2007-09-29 21:35:39 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T13501, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 11501 - Pages differing only in case sensitivity are overridden
Pages differing only in case sensitivity are overridden
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: 3950
  Show dependency treegraph
Reported: 2007-09-29 18:38 UTC by stux
Modified: 2007-09-29 21:35 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description stux 2007-09-29 18:38:45 UTC
Given two different pages that have the same name but differ only in case (current examples I've seen only cover first-letter uppercase vs. all uppercase), the page created first will override the one created afterwards.  

For example, in the english wikipedia [[Mess]] refers to a mess hall, while [[MESS]] described an emulator.  However when linking or navigating to either page, only the former page (the description of a mess hall) would be rendered.  The latter would have to be reached directly by using long-form queries and manipulating the page name directly.  


for a list of examples.  

Note that other mixed-case variations have not been tested and may cause problems as well. 

I am unsure what the severity/priority of this bug should be, as this is my first bug report.  However, I do think it is significant as it prohibits normal users from accessing certain pages in the database.
Comment 1 Daniel Kinzler 2007-09-29 18:44:22 UTC
Looking at your test cases, they all appear to be working as expected. Please make sure the problem is not caused by some custom javascript or oddball browser plugin.
Comment 2 Brion Vibber 2007-09-29 20:15:46 UTC
All fine here.
Comment 3 stux 2007-09-29 21:35:39 UTC
Thank you for the advice Daniel.  After testing different configurations (browser: [firefox/opera], machine, account), I have determined that the problem is with the caching proxy that my machine is connected to.  I apologize for having created an unnecessary bug report.  I'll test more diligently in the future.  Also, should this bug be removed from the case-sensitive tracker (3950)? 

Note You need to log in before you can comment on or make changes to this bug.