Shulou(Shulou.com)06/02 Report--

Editor to share with you how to deal with the JSP Chinese coding problem, I believe most people do not know much about it, so share this article for your reference, I hope you can learn a lot after reading this article, let's go to know it!

The most basic garbled problem

This garbled problem is the simplest garbled problem. Usually new ones show up. It is the garbled code caused by the inconsistent coding of the page.

Html Code:

<% @ page language= "java" pageEncoding= "UTF-8"% > <% @ page contentType= "text/html;charset=iso8859-1"% > < html > < head > < title > Chinese questions < / title > < meta http-equiv= "Content-Type" content= "text/html;charset= UTF-8" > < / head > < / head > < body > I'm a good person < / body > < / html >

The code of three places

The encoding format of * places is the storage format of jsp files. Ecljpse saves the file according to this encoding format. And compile the jsp file, including the Chinese characters.

The second encoding is in decoding format. Because the file saved as UTF-8 is decoded to iso8859-1, there must be garbled codes in Chinese. Which means it has to be consistent. And the second place is in this line, it can be left out. The default is also to use the iso8859-1 encoding format. So if there is no such business, "I am a good person" will also appear garbled. It has to be consistent.

The third encoding is to control the decoding mode of the browser. If the previous decoding is consistent and correct, this encoding format does not matter. Some web pages are garbled because browsers are not sure which encoding format to use. Because pages are sometimes embedded in pages, browsers confuse the coding format. There are garbled codes.

Garbled problems received after the form was submitted in Post mode

This problem is also a common problem. This garbled code is also messed up by tomcat's internal coding format iso8859-1, that is, when post is submitted, if the encoding format is not set, it will be submitted in iso8859-1, while the accepted jsp will be accepted in utf-8. Leading to garbled code. Since this is the case, here are several solutions and compare them.

a. Transcoding when accepting parameters

String str = new String (request.getParameter ("something") .getBytes ("ISO-8859-1"), "utf-8")

In this case, each parameter must be transcoded in this way. It's troublesome. But you can get Chinese characters.

b. At the beginning of the request page, execute the coding code for the request

Request.setCharacterEncoding ("UTF-8")

Set the character set of the submission to UTF-8. In this way, the page that accepts this parameter does not have to be transcoded. Direct use

String str = request.getParameter ("something")

The parameters of Chinese characters can be obtained. But this sentence needs to be executed on every page. This method is also effective for post submissions, but not for enctype= "multipart/form-data" when get submits and uploads files. The garbled code of these two will be explained separately later.

c. To avoid writing request.setCharacterEncoding ("UTF-8") on every page, it is recommended that you use a filter to encode all jsp. There are many examples on this Internet. Please check it for yourself.

Garbled handling of form get submission

If you use get to submit Chinese, the page that accepts parameters will also have garbled code, which is also caused by tomcat's internal coding format iso8859-1. Tomcat will encode Chinese characters with iso8859-1, the default coding mode of get, and append it to url after encoding, resulting in garbled /, and garbled parameters on the acceptance page.

Solution:

a. Use the * * method in the above example to decode the received characters and then transcode them.

B. Get is committed by url, and iso8859-1 has been encoded before entering url. In order to affect this encoding, you need to add the useBodyEncodingForURI= "true" attribute to the Connector node of server.xml to control how tomcat encodes Chinese characters in get mode. The above attribute controls that get submissions are also encoded in the encoding format set by request.setCharacterEncoding ("UTF-8"). So automatically encode it as utf-8 and accept it as normal on the page. But I think the real coding process is that tomcat has to base on

< Connector port= "8080" maxThreads= "150" minSpareThreads= "25" maxSpareThreads= "75" enableLookups= "false" redirectPort= "8443" acceptCount= "100" debug= "0" connectionTimeout= "20000" useBodyEncodingForURI= "true" disableUploadTimeout= "true" URIEncoding= "UTF-8" / >

The URIEncoding= "UTF-8" set in it is encoded again, but since it is already encoded as utf-8, the encoding will not change. If the encoding is obtained from url, the acceptance page is decoded according to the URIEncoding= "UTF-8".

Solve the garbled code when uploading files

When uploading files, the form form is set to enctype= "multipart/form-data". This way the document is submitted as a stream. If you use the upload component of apach, you will find that there is a lot of garbled imagination. This is because the previous commons-fileupload.jar of apach has bug, which takes out the Chinese characters and decodes them, because it is submitted in this way, and the encoding automatically uses the tomcat default encoding format iso-8859-1. But the problem of garbled code is: periods, commas, and other special symbols become garbled. If the number of Chinese characters is odd, there will be garbled, and even numbers will be parsed normally.

Solution:

Downloading this version of jar from commons-fileupload-1.1.1.jar has solved these bug.

However, when you take out the content, you still need to transcode the extracted characters from iso8859-1 to utf-8. All the normal Chinese characters and characters can be obtained.

Java code about url request, accept garbled parameters

The encoding format of url depends on the URIEncoding= "UTF-8" mentioned above. If this coding format is set, it means that all Chinese character parameters to url must be encoded. Otherwise, the parameter values of Chinese characters are garbled, such as a link:

Response.sendDerect ("/ a.jsproomname = Zhang Dawei")

And use it directly in a.jsp.

String name = request.getParameter ("name")

All you get is garbled. Because it is stipulated that it must be utf-8, this turn should be written as follows:

Response.sendDerect ("/ a.jsp?name=URLEncode.encode (" Zhang Dawei "," utf-8 ")

Only then.

What happens if you don't set this parameter URIEncoding= "UTF-8"? If it is not set, the default encoding format iso8859-1 is used. The problem comes out again. * * is the number of parameter values. If the number of parameter values is odd, it can be parsed normally. If you make an even number, you will get * characters that are garbled. In addition, if a character is in English, it can be parsed normally, but the Chinese punctuation marks are still garbled. As a stopgap measure, if you do not have Chinese punctuation in your parameters, you can add an English symbol to the parameter value to solve the garbled problem, and then remove the symbol of the * face after you get the parameter. It can also be put together or used.

Script code about url request, the parameters received are garbled

The script will also control the page redirection, and it will also involve an attached parameter, which will be parsed on the accepting page. If this Chinese character parameter does not carry out the coding processing specified by URIEncoding= "UTF-8", the Chinese characters received by the receiving page are also garbled. Script processing coding is more troublesome, there must be a corresponding coding script corresponding file, and then call the method in the script to encode Chinese characters.

About the garbled code opened by jsp in MyEclipse

For an existing project, the storage format of the Jsp file may be utf-8. If you have a newly installed eclipse, the default encoding format for opening it is iso8859-1. As a result, the Chinese characters in jsp appear garbled. This garbled code is relatively easy to solve. Go directly to eclipse3.1 's preferences and find general- > edidor, and set it to your file to open the code as utf-8. Eclipse will automatically reopen in the new encoding format. Chinese characters can be displayed normally.

About the garbled situation when the html page is opened in eclipse

Since most of the pages are made by dreamweaver, the storage format is different from that of eclipse. In general, create a new jsp in eclipse, copy the page content from dreamweaver and paste it into jsp.

The above is all the contents of this article entitled "how to deal with JSP Chinese coding problems". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.