Last modified: 2010-05-15 15:33:22 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 1951 - Urls with [ and ] do not display properly
Urls with [ and ] do not display properly
Status: RESOLVED DUPLICATE of bug 343
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-04-22 23:06 UTC by Corey Burger
Modified: 2010-05-15 15:33 UTC (History)
0 users

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


Description Corey Burger 2005-04-22 23:06:03 UTC
Urls such as[347]=x-347-65428 do not
display correctly.

My though is that they would need to be escaped in an easy manner. One possible
way would be to use quotes for this. Basically tell the renderer to ignore any [
or ] from " to a close ".
Comment 1 Brion Vibber 2005-04-22 23:17:32 UTC
A couple quick notes for reference: [ and ] are not legal URL characters, so _must_ be escaped per RFC 2396 2.4.3.

We're lax in what we accept, though, so if it's not ambiguous we could take them and do the escaping ourselves.

However [ and ] are special syntax characters to the wiki, used as delimiters for URL and wiki links, so it needs to be done quite carefully if done at 
Comment 2 Corey Burger 2005-04-22 23:28:50 UTC
It would be a lot nicer if non-RFC-compliant URL's didn't exist.
Comment 3 Rowan Collins [IMSoP] 2005-04-24 17:11:17 UTC
Tentatively marking as a dupe of bug 343, based on Brion's comment re the
relevant RFC.

*** This bug has been marked as a duplicate of 343 ***

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