Most of the time, we have javascript for verification on the client, such as mandatory options and format verification. If not, we will not allow form submission. However, it is highly risky to verify important information that is not on the server. The following simple example proves this.
The HTML file is as follows. There are two text input boxes on the page. One ID is name and the other ID is Sechole. Javascript checks the name on the client. For simplicity, the verification rules here are required. After the verification is passed, a servlet is submitted to the server.
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
You can use some plug-ins in the browser, such as firebug in Firefox, to change the Sechole ID to name, and change the name ID to another value. Then, you can "cheat" the browser's Js verification. For example, if no value is entered in the name input box and the value is filled in the security hole box, verification can be passed and the request is submitted successfully.