Remote Validation in ASP.NET MVC when JavaScript is Disabled

Remote Validation in ASP.NET MVC when JavaScript is Disabled

Remote Validation in ASP.NET MVC when JavaScript is Disabled

In this article, I am going to discuss Remote validation in ASP.NET MVC Application when JavaScript is Disabled. Please read our previous article where we discussed Remote validation in the ASP.NET MVC application. In our previous article, we discussed what is Remote Validation and how to implement Remote Validation in MVC. This is a continuation part to our previous article, so please read our previous article before proceeding to this article.  

Remote validation in MVC when javascript is disabled:

The Remote attribute only works when JavaScript is enabled. If the end-user disables JavaScript on his/her machine then the validation does not work. This is because RemoteAttribute requires JavaScript to make an asynchronous AJAX call to the server-side validation method. As a result, the user will be able to submit the form, bypassing the validation in place. This is why it is always important to have server-side validation.

To make server-side validation work, when JavaScript is disabled, there are 2 ways

1. Add model validation error dynamically in the controller action method
2. Create a custom remote attribute and override IsValid() method

原文有这两种的实现方式，可以去原文查看

In the next article, I am going to discuss Action Results in ASP.NET MVC. Here, in this article, I try to explain Remote validation in ASP.NET MVC when javascript is disabled with examples. I hope this article will help you with your need. I would like to have your feedback. Please post your feedback, question, or comments about this article.

 

How to handle validation when JavaScript is disabled in ASP.NET

The validation controls are designed to validate primarily on the server side. The client-side validation is optional (see the EnableClientScript property). So if they aren't working with Javascript disabled, then you're probably missing a little boilerplate code in your page, such as this snippet from the MSDN documentation on Page.IsValid:

private void ValidateBtn_Click(Object Sender, EventArgs E)
{
    Page.Validate();
    if (Page.IsValid == true)  // yes, it is written this way in the MSDN documentation
        lblOutput.Text = "Page is Valid!";
    else
        lblOutput.Text = "Some required fields are empty.";
}

You can also call Page.Validate and check Page.IsValid in your Page's OnLoad event, so that you can prevent a postback from proceeding to the next step when the form needs to be re-submitted. You probably don't even need to call Validate() explicitly — Button.CausesValidation is true by default.

 

作者:Chuck Lu    GitHub