How to solve the problem that ASP.NET detects a potentially dangerous request.form value from the client

This article focuses on "how to solve the potentially dangerous request.form value detected by ASP.NET from the client". Interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to solve the potentially dangerous request.form value detected by ASP.NET from the client.

1. Add code to the current submission page

Open the current .aspx page with the code validateRequest= "false" in the header, such as:

The copy code is as follows:

2. Modify the web.config configuration file globally (this is not recommended and unsafe)

Open the web.config file, and in the middle, add the following code:

The copy code is as follows:

3. Another way to deal with it: the reason is that the passed value contains special danger symbols, so you can use the Server.HtmlEncode (string) method to encode the string before it is passed, so that the dangerous characters will be escaped into ordinary characters. Such as TextBox1.Text=Server.HtmlEncode (str)

At this point, I believe you have a deeper understanding of "how to solve the potentially dangerous request.form value detected by ASP.NET from the client". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!