Design | page
The landing window is the only access to the background, so be sure to put the right one.
Here are some of my own ideas:
There are generally two pages composed of Login.asp chklogin.asp
Login.asp for landing, chklogin.asp for verifying login
Login.asp's main design is: Name, password, verification code.
The verification code is used to prevent violent cracking.
The main design of chklogin.asp is:
1. Verify that the data in the table conveys in the login.asp is legitimate, and if legal data and data in the database
In contrast, it allows landing.
2. It is best to add the ability to prevent forms from being submitted outside the form.
3. Save the legal variable, with session ("name") =
Session ("password") =
Session ("num") = Authentication Code
Or you can use cookies.
Note the problem:
1. Verify data legality, filter special characters, prevent SQL vulnerabilities
2. Prevent forms from being submitted outside the form
Implementation of some code:
Server_v1=cstr (Request.ServerVariables ("Http_referer"))
Server_v2=cstr (Request.ServerVariables ("SERVER_NAME"))
If Mid (Server_v1,8,len (SERVER_V2)) <>server_v2 Then
Response.Write "You submitted the wrong path, prohibit the submission of data from outside the site please do not mess with this parameter!" "
Response.End
End If
