Last modified: 2010-05-15 15:33:22 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 T3951, the corresponding Phabricator task for complete and up-to-date bug report information.
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)
1.4.x
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  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: ---


Attachments

Description Corey Burger 2005-04-22 23:06:03 UTC
Urls such as 
http://www.privacyinternational.org/article.shtml?cmd[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 
all.
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.


Navigation
Links