Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

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 antwurd
  • 1 hat dit probleem
  • 1 werjefte
  • Lêste antwurd fan 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

Keazen oplossing

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.

Dit antwurd yn kontekst lêze 👍 2

Alle antwurden (1)

more options

Keazen oplossing

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.