url-encoding

I use javascript / jquery to fill dom elements that contain umlauts: var text1 = "Unser platonisches Internetreich droht in die H%E4nde einer bewaffneten Miliz zu fallen." $("#quote1 span").html(unescape(text1)); How can I get rid of the url encoding e.g. "H%E4nde" and use "Hände" instead? I tried <meta charset="utf-8" /> <meta name="http-equiv" content="Content-type: text/html; charset=UTF-8"/> <script type="text/javascript" src="js/index.js" charset="utf-8"></script> But none of them seem to work... Thanks for help. That is not UTF-8, that is percent encoding also known as url encoding. You

If I navigate to the following URL with a special UTF8 encoded character I get different results in web browsers: http://example.com/lörickè Firefox 37 - Shows the correct URL as above. Chrome 42 - Shows the correct URL as above. Edge - Shows the correct URL as above. IE 11 - Shows percent encoded URL http://example.com/l%c3%b6rick%c3%a8/ Where can I find a list of browsers and versions that support this feature and are there any announcements of whether the new Microsoft Edge browser supports this. This StackOverflow post highlights the above issue for those interested. unor What is shown in

Is the ampersand the only character that should be encoded in an HTML attribute? It's well known that this won't pass validation: <a href="http://domain.com/search?q=whatever&lang=en"></a> Because the ampersand should be & . Here's a direct link to the validation fail. This guy lists a bunch of characters that should be encoded, but he's wrong. If you encode the first "/" in http:// the href won't work. In ASP.NET, is there a helper method already built to handle this? Stuff like Server.UrlEncode and HtmlEncode obviously don't work - those are for different purposes. I can build my own simple

How can we encode a string using the URL (RFC 1738) standard in C#? The following online tool is converting the strings using this standard http://www.freeformatter.com/url-encoder.html An example of the string I want to convert is test(brackets) and the encoded string should look like: test%28brackets%29 Dirk According to RFC 1738 : Thus, only alphanumerics, the special characters "$-_.+!*'(),", and reserved characters used for their reserved purposes may be used unencoded within a URL. Neither HttpUtility.UrlEncode nor WebUtility.UrlEncode will encode those characters since the standard says

I have a query string parameter value that contains an ampersand. For example, a valid value for the parameter may be: a & b When I generate the URL that contains the parameter, I'm using System.Web.HTTPUtility.UrlEncode() to make each element URL-friendly. It's (correctly) giving me a URL like: http://example.com/foo?bar=a+%26b The problem is that ASP.NET's Request object is interpreting the (encoded) ampersand as a Query String parameter delimiter, and is thus splitting my value into 2 parts (the first has "bar" as the parameter name; the second has a null name). It appears that ASP.NET is