I have been studying for many days and have tried many methods. I have summarized the best methods I have found at the moment:
Let me talk about the basics first:
<%@codepage=65001%>UTF-8
<%@codepage=936%>Simplified Chinese
<%@codepage=950%>Traditional Chinese
<%@codepage=437%>U.S./Canada English
<%@codepage=932%> Japanese
<%@codepage=949%>Korean
<%@codepage=866%>Russian
codepage specifies what code IIS reads the passed string (form submission, address bar delivery, etc.).
The reason for garbled code is that the module encoding is different when the website needs to be integrated.
Just like my blog, this problem occurs when integrating because BLOG is Utf-8.
Recently, many netizens have been consulting on this issue, and I have tried many methods.
The most convenient method is as follows:
Do not convert any module web page encoding the utf-8 or utf-8, and the Gb22312 or Gb2312
In the Utf-8 module package file (such as conn.asp, but be aware that conn.asp must be called on the first line) add the first line to the front of the package file (such as conn.asp, but be aware that conn.asp must be called on the first line).
<%@LANGUAGE="VBSCRIPT"CODEPAGE="65001"%>
<%Session.CodePage=65001%>
Add in front of the package file of GB2312 module
<%@LANGUAGE="VBSCRIPT"CODEPAGE="936"%>
<%Session.CodePage=936%>
Other encodings and so on.