好吧，我还是可以回答的。

除了Rob和Nathan的回答，我还想补充一点，客户端验证很重要。当你在你的web表单上应用验证时，你必须遵循以下准则:

客户端

必须使用客户端验证，以过滤来自您网站的真实用户的真实请求。 应该使用客户端验证来减少在服务器端处理期间可能发生的错误。 应该使用客户端验证来最小化服务器端往返，从而节省带宽和每个用户的请求。

服务器端

You SHOULD NOT assume the validation successfully done at client side is 100% perfect. No matter even if it serves less than 50 users. You never know which of your user/emplyee turn into an "evil" and do some harmful activity knowing you dont have proper validations in place. Even if its perfect in terms of validating email address, phone numbers or checking some valid inputs it might contain very harmful data. Which needs to be filtered at server-side no matter if its correct or incorrect. If client-side validation is bypassed, your server-side validations comes to rescue you from any potential damage to your server-side processing. In recent times, we have already heard lot of stories of SQL Injections and other sort of techniques that might be applied in order to gain some evil benefits.

Both types of validations play important roles in their respective scope but the most strongest is the server-side. If you receive 10k users at a single point of time then you would definitely end up filtering the number of requests coming to your webserver. If you find there was a single mistake like invalid email address then they post back the form again and ask your user to correct it which will definitely eat your server resources and bandwidth. So better you apply javascript validation. If javascript is disabled then your server side validation will come to rescue and i bet only a few users might have accidentlly disable it since 99.99% of websites use javascript and its already enabled by default in all modern browsers.

如果您正在进行轻量级验证，最好在客户端上进行。它将节省网络流量，这将帮助您的服务器更好地运行。如果验证很复杂，需要从数据库中提取数据或密码之类的东西，那么最好在可以安全地检查数据的服务器上进行验证。

好吧，我还是可以回答的。

除了Rob和Nathan的回答，我还想补充一点，客户端验证很重要。当你在你的web表单上应用验证时，你必须遵循以下准则:

客户端

必须使用客户端验证，以过滤来自您网站的真实用户的真实请求。 应该使用客户端验证来减少在服务器端处理期间可能发生的错误。 应该使用客户端验证来最小化服务器端往返，从而节省带宽和每个用户的请求。

服务器端

You SHOULD NOT assume the validation successfully done at client side is 100% perfect. No matter even if it serves less than 50 users. You never know which of your user/emplyee turn into an "evil" and do some harmful activity knowing you dont have proper validations in place. Even if its perfect in terms of validating email address, phone numbers or checking some valid inputs it might contain very harmful data. Which needs to be filtered at server-side no matter if its correct or incorrect. If client-side validation is bypassed, your server-side validations comes to rescue you from any potential damage to your server-side processing. In recent times, we have already heard lot of stories of SQL Injections and other sort of techniques that might be applied in order to gain some evil benefits.

Both types of validations play important roles in their respective scope but the most strongest is the server-side. If you receive 10k users at a single point of time then you would definitely end up filtering the number of requests coming to your webserver. If you find there was a single mistake like invalid email address then they post back the form again and ask your user to correct it which will definitely eat your server resources and bandwidth. So better you apply javascript validation. If javascript is disabled then your server side validation will come to rescue and i bet only a few users might have accidentlly disable it since 99.99% of websites use javascript and its already enabled by default in all modern browsers.

必须始终在服务器上进行验证。

在客户端上进行验证对用户来说也很好，但这是完全不安全的。

JavaScript可以在运行时修改。

我建议在服务器上创建验证结构，并与客户端共享该结构。

你需要在两端单独的验证逻辑，例如:

客户端输入的“必需”属性

字段。长度> 0服务器端。

但是使用相同的验证规范将消除两端镜像验证的一些冗余(和错误)。

您可以进行服务器端验证，并将每个字段的验证结果发送回一个JSON对象，将客户端Javascript保持在最低限度(只显示结果)，并且仍然具有用户友好的体验，而无需在客户端和服务器上重复。