07 May 2010
22 Jun 2010
Link to this post
Well, a domain name is a part of a url, isn't it? Surely then, a url can, unencoded contain non RFC 1738-specified characters? Furthermore, there's HttpUtility.UrlEncode, which you can use, (if you are afraid of the consequences of not encoding), which would encode the utf-8 characters with url-allowed characters.
In order to test my theory and ensure I'm not rambling I just created a test-case:
or in non-encoded form: http://haf.se/åäö.aspx
As you can see, there are no problems what so ever with having non ASCII-characters in the URL.
Now, I consider this a bug of Sitefinity, don't you? If you choose to fix this bug, please don't encode the links; that's done by the browser and it would look bad with url-encoded links.