Under certain conditions, you may need to bypass verification. For example, you might have a page that should be able to send even if the user doesn't fill out all the validation fields correctly. You can set up ASP.NET server controls to bypass client and server authentication, not just client authentication.
Security Note: By default, ASP.NET web pages perform request validation to ensure that user input does not contain script or HTML elements. This feature can be disabled explicitly.
You can also disable the validation control so that it does not render on the page at all and validation using the control does not occur.
If you want to perform validation on the server but not on the client, you can set the individual validation controls to not generate client scripts. This is especially useful if dynamic updates on the client cause problems with the layout of the page, or if some server code needs to be executed before validation.
1. Disable validation in specific controls
Set the control's CausesValidation property to false.
The following example shows how to create a Cancel button so that it bypasses the validation check:
<asp:Button id="Button1" runat="server"
Text="Cancel" CausesValidation="False">
</asp:Button>
2. Disable verification controls
Set the validation control's Enabled property to false.
3. Disable client verification
Set the validation control's EnableClientScript property to false.
This article comes from the CSDN blog. Please indicate the source when reprinting: http://blog.csdn.net/dodream/archive/2009/12/17/5024653.aspx