CN108089849B - Method for preventing cheating program from being rapidly submitted - Google Patents

Abstract

The invention relates to the technical field of website development, in particular to a method for preventing cheating programs from being rapidly submitted. The method comprises the steps that a server generates a random number as a salt value and stores the salt value in a session, a page carries out hash calculation on the salt value on an answer through a script, and the answer starts from 0 until the obtained hash value meets the requirement; when the form is submitted, the answer is submitted together; and checking whether the answer meets the requirements at the server side so as to identify whether cheating behaviors exist. The invention solves the problems that the common form page is easy to be cracked by a cheating program and can be rapidly and repeatedly submitted with junk advertisement information in a short time.

Description

Method for preventing cheating program from being rapidly submitted

Technical Field

The invention relates to the technical field of website development, in particular to a method for preventing cheating programs from being rapidly submitted.

Background

Currently, the website form submission page usually adopts verification codes and measures for limiting the submission time interval of a single IP to prevent a cheated program from submitting spam repeatedly and quickly. However, with the technical progress, the verification code is easy to be identified and cracked, the verification code which is difficult to be identified influences the user experience, and the IP limitation is easy to be automatically replaced and cracked by the cheating program.

Disclosure of Invention

The technical problem to be solved by the invention is to provide a method for preventing a cheating program from being rapidly submitted, and solve the problems that the user experience is influenced and the cheating program is easy to crack by the existing verification code and IP limiting mode.

The technical scheme for solving the technical problems is as follows:

the method comprises the steps that a server generates a random number as a salt value and stores the salt value in a session, a page carries out hash calculation on an answer through a script, and the answer starts from 0 until the obtained hash value meets the requirement; when the form is submitted, the answer is submitted together; and checking whether the answer meets the requirements at the server side so as to identify whether cheating behaviors exist.

The method comprises the following steps:

step one, when a form page is initialized, a server generates a random number and stores the random number in the form page

session [ "contention" ];

step two, the front-end page performs Hash calculation of a salt value in the script by using the generated random number to obtain a Hash value of an answer, and the answer starts from 0 until the calculated Hash value meets the requirement;

step three, when the user submits the form, the answer is used as a parameter value and submitted to the server side, if the calculation is not completed at the moment, the user is prompted to submit too fast, and the calculation is waited to be completed;

and step four, the server side uses the received answer parameter value, takes the value of the session [ "request" ] as a salt value, calculates a Hash value, and checks whether the answer is correct, thereby judging whether cheating behaviors exist.

If the answer check is correct, the cheating behavior is determined to be absent.

The invention has the beneficial effects that: calculating a Hash value on the page by using the generated salt value to obtain a specified result; although a certain amount of time is consumed, the user does not perceive and influence the user experience because the form filling is performed simultaneously with the user. The defense measures of the invention are different from the verification codes, and the common cheating program is difficult to crack. Even if the cheating program calculates and submits the Hash value according to the requirement, certain time is consumed; thereby preventing the spamming program from rapidly submitting spam. The method can be matched with the traditional verification code, IP limitation and other measures, and greatly limits the action of cheating programs.

Drawings

The invention is further described below with reference to the accompanying drawings:

FIG. 1 is a flow chart of the method of the present invention.

Detailed Description

As shown in fig. 1, the present invention employs the following steps:

step one, when a form page is initialized, a server generates a 4-bit random positive integer and stores the integer in a session [ "query" ];

Random rd＝new Random()；

int question＝rd.Next(1000,9999)；

session["question"]＝question；

step two, the front-end page uses the generated random number as a salt value in the script to calculate the Hash value of an answer, the answer starts from 0, and the characters are '1111' until the first 4 characters of the Hash value are obtained through calculation;

step three, when the user submits the form, the answer is used as a parameter value and submitted to the server side, if the calculation is not completed at the moment, the user is prompted to submit too fast, and the calculation is waited to be completed;

and step four, the server side uses the received answer parameter value, takes the value of the session [ "request" ] as a salt value, calculates a Hash value, and checks whether the answer is correct, thereby judging whether cheating behaviors exist.

Claims (2)

1. A method for preventing a cheating program from being quickly committed, comprising: the method comprises the steps that a server generates a random number as a salt value and stores the salt value in session, a page carries out Hash calculation on an answer through a script, the answer starts from 0 until 4 characters before the Hash value obtained through calculation are 1111%; when the form is submitted, the answer is submitted together; and checking whether the answer meets the requirements at the server side so as to identify whether cheating behaviors exist.

2. The method of claim 1, wherein: the method comprises the following steps:

step one, when a form page is initialized, a server generates a random number and stores the random number in a session [ "query" ];

step two, the front-end page performs Hash calculation of a salt value in the script by using the generated random number to obtain a Hash value of an answer, wherein the answer starts from 0 until 4 characters before the calculated Hash value are '1111';

step three, when the user submits the form, the answer is used as a parameter value and submitted to the server side, if the calculation is not completed at the moment, the user is prompted to submit too fast, and the calculation is waited to be completed;

and step four, the server side uses the received answer parameter value, takes the value of the session [ "request" ] as a salt value, calculates a Hash value, and checks whether the answer is correct, thereby judging whether cheating behaviors exist.

Images