ASP server error message garbled_html/css_WEB-ITnose

Dear heroes, I wonder if the IE browser version is too low and the settings page is garbled. It's just that the ASP server error message is garbled.

The following is UTF-8


The following is Simplified Chinese

The following is compatible

Reply to discussion (solution)

The web page can set the encoding, but you definitely have not set it.

If you find garbled characters when browsing the page. You can try these steps: Make sure that the encoding format of your page is correct: for example, if you use charset=utf-8 in test.asp, please first make sure that the file itself is Utf-8 encoded. You can use Notepad to convert. Similarly, if you use charset=GBK, please first ensure that the file itself is GBK encoded.
Make sure that the encoding method of the original data you get (such as the data obtained from the database) is consistent with the page encoding method.
Try to specify what encoding IIS reads in.
<%@ codepage=65001%>UTF-8
<%@ codepage=936%>Simplified Chinese
<%@ codepage=950%>Traditional Chinese
< ;%@ codepage=437 %>US/Canada English
<%@ codepage=932 %>Japanese
<%@ codepage=949 %>Korean
<%@ codepage= 866 %>Russian
codepage specifies what encoding IIS reads.
For example, if UTF-8 encoding is used, add <%@LANGUAGE="VBSCRIPT" CODEPAGE="65001"%> at the top of the file.
For example, if GBK encoding is used, add On <%@LANGUAGE="VBSCRIPT" CODEPAGE="936"%>
Set the asp built-in object symbol mapping and the encoding of the response content-type header
If you use utf-8 encoding, just at the end of the article Add above:
<% Session.CodePage=65001
Response.Charset="UTF-8" %>
If you use GBK encoding, add at the top of the article:
<% Session.CodePage=936
Response.Charset="GBK" %>
Note that you can put the settings pointed out in 3 and 4 into a publicly included file (such as conn.asp) top. Then all pages apply this attribute.

Thank you, 2nd floor. The asp program is 65001 and the IE browser is utf-8. It should be fine.
The content of the page is displayed normally, only the error message returned is garbled!

Some programs are 936, is this related? I'll try.

The problem is solved, CODEPAGE="65501", and the subsequent charset=GB2312" are inconsistent. The previous one is changed to 936, that's good.