This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

This thread was archived. Əgər kömək lazımdırsa lütfən yeni sual verin.

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 cavab
  • 1 has this problem
  • 2 views
  • Last reply by knorretje

lolwut22
lolwut22
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

Chosen solution

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.

Read this answer in context 👍 2

All Replies (1)

knorretje
knorretje
more options

Seçilmiş Həll

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.