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.

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

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 réponse
  • 1 a ce problème
  • 1 vue
  • Dernière réponse par 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

Solution choisie

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.

Lire cette réponse dans son contexte 👍 2

Toutes les réponses (1)

more options

Solution choisie

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.