Xheditor detects potentially dangerous request. Form values from the client.

Oh, God!

When xheditor is triggered in the middle of the night, if there are no special characters such as carriage return, no error will be reported, but an error such as carriage return will be reported immediately.

 

A potentially dangerous request. form value is detected from the client (elm1 = "<p> 6y5y5yr5yy </P> <p>.

Depend on me
!

I have studied how to add web. config

<System. Web>

<Httpruntime requestvalidationmode = "2.0" type = "codeph" text = "/codeph"/>

</Authentication>

Then, <% @ page Language = "C #" autoeventwireup = "true" codebehind = "content_add.aspx.cs" inherits = "JLP. content_add" validaterequest = "false" %>
Add validaterequest = "false". I will circle the cross.

Note:
Please
The verification process detects a potentially dangerous client input value, and the processing of the request has been aborted. This value may indicate attempts to compromise application security, such as cross-site scripting attacks. To allow page Rewriting
Set request verification in sequence. Set the requestvalidationmode feature in the httpruntime configuration section
Requestvalidationmode = "2.0 ". Example: Requestvalidationmode = "2.0"/>. After setting this value, you can use the page command or <pages>
Set validaterequest = "false" in the configuration section"
Disable request verification. However, in this case, it is strongly recommended that the application explicitly check all input. For more information, see

Http://go.microsoft.com/fwlink? Linkid = 153133.

 

Fool! There are !!!!!!!!!!!!!!!!!