The garbled problem caused by the Chinese parameter of JS URL

Today's project encountered a garbled problem, from JS to the URL to the server, the URL has Chinese parameters, the server read the Chinese parameters are all "? ", check the online JS coding related data to solve.

Workaround One:

1, in JS in the Chinese parameter two times transcoding

var login_name = document.getElementById ("loginname"=

2. Decoding the parameters on the server side

String loginName = paramutil.getstring (Request, "login_name"

When using a URL for parameter passing, some Chinese name arguments or URL addresses are often passed, and conversion errors occur during background processing. In some pass-through pages use GB2312, and the Receive page uses UTF8, so that the received parameters may be inconsistent with the original. URLs that are encoded using the server-side UrlEncode function are not the same as the URLs encoded with the encodeURI function of client JavaScript.

Workaround Two:

Front desk:

login_name = encodeURIComponent (login_name);//Encode once

In action:

New String (Keyword.getbytes ("iso-8859-1"), "Utf-8"= Urldecoder.decode (temp, "utf-8");//keyword is the parameter name

Coding methods in javascript:

Escape () Method:

Encodes the specified string using the ISO Latin character set. All space characters, punctuation marks, special characters, and other non-ASCII characters are converted to the character encoding in the%xx format (XX equals the encoded 16-digit number of the character in the character set table). For example, the encoding for a space character is%20. The Unescape method is the opposite. Characters that are not encoded by this method: @ */+

If it is gb2312 encoding can use escape, cannot use encodeuricomponent, not garbled.

How to use escape: http://www.jb51.net/w3school/jsref/jsref_escape.htm

English explanation: MSDN JScript reference:the Escape method returns a string value (in Unicode format) that contains the contents of [t He argument]. All spaces, punctuation, accented characters, and any other non-ascii characters is replaced with%XX encoding, where xx is equivalent to the hexadecimal number representing the character. For example, a space is returned as "%20."
Edge Core Javascript guide:the escape and unescape functions let you encode and decode strings. The escape function returns the hexadecimal encoding of a argument in the ISO Latin character set. The Unescape function returns the ASCII string for the specified hexadecimal encoding value.

encodeURI () Method: Converts the URI string into an escape format using the UTF-8 encoding format. Characters that will not be encoded by this method:! @ # $& * () =:/;? +

English explanation: MSDN JScript reference:the encodeURI method returns an encoded URI. If you pass the result of the decodeURI, the original string is returned. The encodeURI method does not encode the following characters: ":", "/", ";", and "?". Use encodeURIComponent to encode these characters. Edge Core Javascript guide:encodes a Uniform Resource Identifier (URI) by replacing each instance of certain characters B Y one, one, or three escape sequences representing the UTF-8 encoding of the character

encodeURIComponent () Method: Converts the URI string into an escape format using the UTF-8 encoding format. Compared to encodeURI (), this method encodes more characters, such as characters. So if the string contains several parts of the URI, it cannot be encoded in this way, otherwise the URL will display an error after the/character is encoded. Characters that will not be encoded by this method:! * ( )

English explanation: MSDN JScript reference:the encodeURIComponent method returns an encoded URI. If you pass the result of the decodeURIComponent, the original string is returned. Because the encodeURIComponent method encodes all characters, be careful if the string represents a path such as/folder1/ Folder2/default.html. The slash characters would be encoded and would is not being valid if sent as a request to a Web server. Use the encodeURI method if the string contains more than a single URI component. Mozilla Developer Core Javascript guide:encodes a Uniform Resource Identifier (URI) component by replacing each instance of certain characters by one, both, or three escape sequences representing the UTF-8 encoding of the character.

Therefore, for the Chinese string, if you do not want to convert the string encoding format into UTF-8 format (such as the original page and the target page charset is consistent), only need to use escape. If your page is GB2312 or other encoding, and the page that accepts the parameter is UTF-8 encoded, it is necessary to use encodeURI or encodeuricomponent.

In addition, Encodeuri/encodeuricomponent is introduced after javascript1.5, and escape is available in the javascript1.0 version.  

English Note: The Escape () method does not encode the + character which are interpreted as a space on the server side as well as Gen Erated by forms with spaces in their fields. Due to the shortcoming, you should avoid use of escape () whenever possible. The best alternative is usually encodeuricomponent (). Use of the encodeURI () method was a bit more specialized than escape () in that it encodes for URIs [REF] as opposed to the QueryString, which is part of a URL. Use this method when you need to encode a string to is used for any resource that uses URIs and needs certain characters T O remain un-encoded. Note that this method does not encode the ' character, as it is a valid character within uris.lastly, the Encodeuricompone NT () method should is used in the most cases when encoding a single component of a URI. This method would encode certain chars that would normally being recognized as special chars for URIs so, many components May is included. Note that this method does not encode the ' character, as it is a valid character within URIs.

This article transferred from: http://www.jb51.net/article/19850.htm

http://blog.csdn.net/elfenliedef/article/details/6115152

The garbled problem caused by the Chinese parameter of JS URL