Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

when i open an irc link with a channel name that contains "~" at the end, firefox (14.0.1) opens the same channel name but with "%7E" instead of "~" at the end

  • 1 baphendule
  • 1 inale nkinga
  • 2 views
  • Igcine ukuphendulwa ngu knorretje

more options

when i open an irc link with a channel name that contains "~" at the end firefox (14.0.1) opens the same channel name but with "%7E" instead of "~" at the end http://img835.imageshack.us/img835/2856/clipboard05nq.jpg

when i open an irc link with a channel name that contains "~" at the end firefox (14.0.1) opens the same channel name but with "%7E" instead of "~" at the end http://img835.imageshack.us/img835/2856/clipboard05nq.jpg

Isisombululo esikhethiwe

I can not open the image, but I can say something in general about the tilde.
The tilde "~" is an unreserved character and therefore it can be replaced by its percent-encoded form "%7E" inside a URI without changing meaning. See
http://en.wikipedia.org/wiki/Percent-encoding
According to section 2.3 of RFC3986 we should prefer the unencoded form so this behavior seems to be a bit out-dated.

Funda le mpendulo ngokuhambisana nalesi sihloko 👍 2

All Replies (1)

more options

Isisombululo Esikhethiwe

I can not open the image, but I can say something in general about the tilde.
The tilde "~" is an unreserved character and therefore it can be replaced by its percent-encoded form "%7E" inside a URI without changing meaning. See
http://en.wikipedia.org/wiki/Percent-encoding
According to section 2.3 of RFC3986 we should prefer the unencoded form so this behavior seems to be a bit out-dated.