CN114564353A - Data verification method and device, electronic equipment and storage medium - Google Patents
Data verification method and device, electronic equipment and storage mediumDownload PDFInfo
- Publication number
- CN114564353A CN114564353ACN202210175849.7ACN202210175849ACN114564353ACN 114564353 ACN114564353 ACN 114564353ACN 202210175849 ACN202210175849 ACN 202210175849ACN 114564353 ACN114564353 ACN 114564353A
- Authority
- CN
- China
- Prior art keywords
- data
- verification
- verified
- rule
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3041—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is an input/output interface
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
Description
Technical Field
The embodiment of the invention relates to the technical field of data processing, in particular to a data verification method and device, electronic equipment and a storage medium.
Background
The data verification of the front end and the back end is used as an important component of data processing in the internet field, has the advantage of timely discovering potential safety hazards, and can help operation and maintenance personnel to quickly locate potential safety hazard points and timely carry out operation and maintenance.
At present, the front end and the back end respectively carry out data verification according to business rules and data requirements, and when the data are actually verified, the situation that the front end fails to verify or the front end passes by the back end to be verified and is not subjected to secondary verification often occurs, so that the problems that verification behaviors are not controllable and user experience is poor exist in the existing data verification of the front end and the back end are caused.
Disclosure of Invention
The embodiment of the invention provides a data verification method, a data verification device, electronic equipment and a storage medium, which can flexibly and controllably verify data at the front end and the back end and improve user experience.
In a first aspect, an embodiment of the present invention provides a data verification method, including:
responding to the data submission request, and acquiring a data verification type matched with the data submission request, wherein the data verification type comprises: front end verification and/or back end verification;
feeding back a data input page matched with the data submission request, and receiving data to be verified through the data input page;
and carrying out data verification matched with the data verification type on the data to be verified.
In a second aspect, an embodiment of the present invention further provides a data verification apparatus, including:
the data acquisition module is used for responding to the data submission request and acquiring a data verification type matched with the data submission request, wherein the data verification type comprises: front end verification and/or back end verification;
the data receiving module to be verified is used for feeding back a data input page matched with the data submitting request and receiving the data to be verified through the data input page;
and the data verification module is used for verifying the data to be verified, wherein the data to be verified is matched with the data verification type.
In a third aspect, an embodiment of the present invention further provides an electronic device, where the electronic device includes:
one or more processors;
storage means for storing one or more programs;
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the data verification method provided by any embodiment of the invention.
In a fourth aspect, an embodiment of the present invention further provides a computer storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the data verification method provided in any embodiment of the present invention.
According to the technical scheme of the embodiment, the data verification type which is matched with the data submission request and comprises front-end verification and/or back-end verification is obtained in response to the data submission request, the data input page matched with the data submission request is fed back, the data to be verified is received through the data input page, and therefore the data to be verified is subjected to data verification matched with the data verification type. Because the data verification type matched with the data submission request comprises front-end verification, back-end verification and any one of the front-end verification and the back-end verification, the data to be verified can be flexibly selected according to actual verification requirements when the data to be verified is verified and matched with the data verification type, the problems that data verification behaviors of the front end and the back end are not controllable and user experience is poor in the prior art are solved, the data of the front end and the back end can be flexibly and controllably verified, and the user experience is improved.
Drawings
Fig. 1 is a flowchart of a data verification method according to an embodiment of the present invention;
fig. 2 is a flowchart of a data verification method according to a second embodiment of the present invention;
FIG. 3 is a flow chart of the online transaction data processing based on the rule engine according to the second embodiment of the present invention;
fig. 4 is a schematic diagram of a data verification apparatus according to a third embodiment of the present invention;
fig. 5 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention.
It should be further noted that, for the convenience of description, only some but not all of the relevant aspects of the present invention are shown in the drawings. Before discussing exemplary embodiments in greater detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but could have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, subprograms, and the like.
Example one
Fig. 1 is a flowchart of a data verification method according to an embodiment of the present invention, where the present embodiment is applicable to a case of flexibly verifying a front end and a back end, and the method may be executed by a data verification apparatus, and the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device. The electronic device may be a terminal device, a server device, or the like, and the embodiment of the present invention does not limit the type of the electronic device that executes the data verification method. Accordingly, as shown in fig. 1, the method comprises the following operations:
and S110, responding to the data submission request, and acquiring the data verification type matched with the data submission request.
The data submission request may be a request for obtaining the required data. For example, the data submission request may include a request to submit a desired page, a request to submit a desired database, and the like. The embodiment of the invention does not limit the data type of the required data submitted by the data submission request. The data check type may be a category of data check operation for distinguishing different data check operations. The data check type may include: front-end verification and/or back-end verification. The front-end check may be a check on the side directly interacting with the user. The back-end check may be a check at the end of the indirect interaction with the user that matches the front-end. Illustratively, the front-end check may include a client check, and the like. The back-end verification may include server-side verification, etc. It can be understood that when the front-end check is a client check, the back-end check is a server check.
In the embodiment of the invention, after the data submission request is received, the data submission request can be responded, so that the data verification type matched with the data submission request is obtained through the analysis of the data submission request. Optionally, the data submission request has a one-to-one correspondence with the data verification type, and the data verification type matched with the data submission request needs to be set according to the verification requirement, for example, the data verification type matched with the data submission request may be set as any one of front-end verification, back-end verification, and front-end verification and back-end verification.
And S120, feeding back a data input page matched with the data submission request, and receiving the data to be verified through the data input page.
The data input page can be an interface capable of inputting data, and the data submission request and the data input interface have a one-to-one correspondence relationship. The data to be verified can be data which is input into the data input interface and needs to be verified.
In the embodiment of the invention, the type of the required request data can be determined according to the data submission request, the data input page matched with the data submission request is further determined according to the type of the required request data, the data input page matched with the data submission request is further displayed for a user to input data through the data input page, and the data to be verified is further received through the data input page.
And S130, performing data verification matched with the data verification type on the data to be verified.
In the embodiment of the invention, the data to be verified can be subjected to data verification according to the data verification type matched with the data submission request and the verification rule matched with the data verification type.
According to the technical scheme of the embodiment, the data verification type which is matched with the data submission request and comprises front-end verification and/or back-end verification is obtained in response to the data submission request, the data input page matched with the data submission request is fed back, the data to be verified is received through the data input page, and therefore the data to be verified is subjected to data verification matched with the data verification type. Because the data verification type matched with the data submission request comprises the front end verification, the back end verification and any one of the front end verification and the back end verification, the actual verification requirement can be flexibly selected when the data to be verified is subjected to the data verification matched with the data verification type, the problems that the data verification behavior of the front end and the data verification behavior of the back end are uncontrollable and the user experience is poor in the prior art are solved, the data of the front end and the back end can be flexibly and controllably verified, and the user experience is improved.
Example two
Fig. 2 is a flowchart of a data verification method according to a second embodiment of the present invention, which is embodied based on the second embodiment, and in this embodiment, a specific optional implementation manner is provided for acquiring a data verification type matching with a data submission request and performing data verification on data to be verified, where the data verification type matches with the data verification type. Specifically, when the target verification control field matched with the target rule verification interface is obtained, the method may further include: acquiring a target check rule matched with the target rule check interface; the specific process of performing data verification matching with the data verification type on the data to be verified may be as follows: and performing data verification matched with the data verification type on the data to be verified by adopting a target verification rule. Accordingly, as shown in fig. 2, the method includes the following operations:
s210, responding to the data submission request, acquiring a data verification type matched with the data submission request, and acquiring a target verification rule matched with the target rule verification interface.
The target rule check interface may be a predefined function or a contract for connection of different components of the software system, and is used to obtain the check rule matching the data submission request. The target verification rule may be a verification rule matched with the data call request, and is used for verifying the data to be verified. The target validation rules may be stored in a target rule validation interface of the rule engine. The rule engine is developed from an inference engine, is a component embedded in an application program, realizes the separation of a business decision from an application program code, writes the business decision by using a predefined semantic template, can receive data input, explains the business rule, and can make the business decision according to the business rule. Illustratively, a rule engine can be separately created outside the back-end, the back-end interacts with the rule engine through an interface to realize data verification, and the back-end can be embedded in a rule engine component and a target rule verification interface provided by the back-end calling component is used for realizing data verification.
In the embodiment of the invention, when the data submission request is responded, the data verification type matched with the data submission request can be obtained, the target rule verification interface matched with the data submission request is determined according to the data submission request, and the data in the target rule verification interface is analyzed to obtain the target verification rule matched with the target rule verification interface.
In an optional embodiment of the present invention, obtaining the data check type matching the data submission request may include: identifying a data submission type matching the data submission request; acquiring a data submission type, and determining a target rule checking interface of a rule engine; acquiring a target verification control field matched with the target rule verification interface, wherein the target verification control field can comprise a front-end verification control field and a rear-end verification control field;
the data submission type may be a data type of the required data that needs to be obtained by the data submission request. The target check control field may be a field configured in the target rule check interface for determining the data check type. The front-end check control field and the back-end check control field may be used to indicate a data check type. The front-end verification control field may be a control field of front-end verification preset according to verification requirements, that is, whether to perform front-end verification may be determined through the front-end verification control field. The back-end verification control field may be a control field of back-end verification preset according to a verification requirement, that is, whether to perform back-end verification may be determined by the back-end verification control field.
In the embodiment of the invention, the data submission type matched with the data submission request can be identified through analyzing the data submission request, and then the target rule verification interface matched with the data submission request in the rule engine is called according to the data submission type, so that the configuration data of the target rule verification interface can be analyzed to obtain the target verification control field matched with the target rule verification interface, namely the front-end verification control field and the back-end verification control field can be obtained through the analysis result of the configuration data of the target rule verification interface. After the front-end verification control field and the back-end verification control field are obtained, the data verification type matched with the data submission request can be determined according to the front-end verification control field and the back-end verification control field.
S220, feeding back a data input page matched with the data submitting request, and receiving the data to be verified through the data input page.
And S230, performing data verification matched with the data verification type on the data to be verified by adopting a target verification rule.
In the embodiment of the invention, data verification can be performed on the data to be verified at the front end and/or the back end through the target verification rule according to the data verification type matched with the data submission request.
In an optional embodiment of the present invention, performing data verification matching the data verification type on the data to be verified by using the target verification rule may include: when the front-end check control field is determined to be the front-end check opening field and the rear-end check control field is determined to be the rear-end check opening field, front-end data to be checked in the data to be checked is checked according to the target check rule, and rear-end data to be checked in the data to be checked is checked according to the target check rule.
The front-end check opening field may be a field that is determined according to the front-end check control field and represents the opening of the front-end check. The back-end check opening field may be a field that is determined according to the back-end check control field and that characterizes the opening of the back-end check. The front-end data to be verified may be data to be verified that needs to be verified at the front end. The data to be verified at the back end may be data to be verified which needs to be verified at the back end. Optionally, the data content of the front-end data to be verified and the data content of the back-end data to be verified may be partially the same or all the same.
In the embodiment of the invention, the target check control field matched with the target rule check interface can be analyzed, and then the front-end check control field and the back-end check control field are determined, so that the field contents of the front-end check control field and the back-end check control field are respectively identified. And if the front-end check control field is a front-end check opening field and the rear-end check control field is a rear-end check opening field, checking the front-end data to be checked in the data to be checked according to the target check rule, and checking the rear-end data to be checked in the data to be checked according to the target check rule so as to realize the check of the same rule on the front end and the rear end.
Illustratively, aiming at the online product transaction processes of financial industries such as banks and the like, the transaction data is required to be verified, and meanwhile, a client is added to perform pre-verification based on the same target verification rule. Therefore, invalid data requests can be effectively shielded at the client, and malicious transactions can be effectively screened out through comparison of the verification results of the front end and the back end, so that financial risk prevention and control are enhanced. The data verification method can realize double verification of the client and the server based on the same target verification rule.
In an optional embodiment of the present invention, after verifying the front-end data to be verified in the data to be verified according to the target verification rule, the method may further include: acquiring front-end default verification data, and verifying the front-end data to be verified in the data to be verified according to the front-end default verification data; after verifying the back-end data to be verified in the data to be verified according to the target verification rule, the method may further include: and acquiring back-end default verification data, and verifying the back-end data to be verified in the data to be verified according to the back-end default verification data.
The front-end default verification data may be preset, and is used for verifying the verification data of the front-end data to be verified, and is different from the target verification rule. The back-end default verification data may be preset, and is used for verifying the verification data of the back-end data to be verified, and is different from the target verification rule. For example, the front-end default verification data may be used to verify a data range, a maximum value, a minimum value, and the like in the front-end data to be verified. The back-end default verification data can be used for verifying the data range, the maximum value, the minimum value and the like in the back-end data to be verified
In the embodiment of the invention, the front-end default verification data and the back-end default verification data can be set according to the known front-end and back-end conventional verification, and then after the front-end data to be verified in the data to be verified is verified according to the target verification rule, the front-end data to be verified in the data to be verified is further verified through the front-end default verification data, so that after the back-end data to be verified in the data to be verified is verified according to the target verification rule, the back-end data to be verified in the data to be verified is verified through the back-end default verification data.
In an optional embodiment of the present invention, performing data verification matching the data verification type on the data to be verified by using the target verification rule may include: when the front-end check control field is determined to be the front-end check closing field and the rear-end check control field is determined to be the rear-end check opening field, front-end data to be checked in the data to be checked is checked according to the front-end default check data, and rear-end data to be checked in the data to be checked is checked according to the target check rule.
The front-end check closing field may be a field that is determined according to the front-end check control field and represents closing of the front-end check.
In the embodiment of the invention, the target check control field matched with the target rule check interface can be analyzed, so that the front-end check control field and the back-end check control field are determined, and the field contents of the front-end check control field and the back-end check control field are respectively identified. If the front-end check control field is a front-end check closing field and the rear-end check control field is a rear-end check opening field, the front-end data to be checked in the data to be checked is checked according to the front-end default check data, the rear-end data to be checked in the data to be checked is checked according to the target check rule, whether the front end and the rear end check control field pass through the same target check rule or not is controlled through setting of the front-end check control field and the rear-end check control field, flexible check of the front end and the rear end for the target check rule is achieved, and the client and the server can be controlled to check respectively.
In an optional embodiment of the present invention, performing data verification matching the data verification type on the data to be verified by using the target verification rule may include: and when the front-end verification control field is determined to be the front-end verification opening field and the rear-end verification control field is determined to be the rear-end verification closing field, verifying the front-end data to be verified in the data to be verified according to the target verification rule, and verifying the rear-end data to be verified in the data to be verified according to the rear-end default verification data.
The backend verification closing field may be a field that is determined according to the backend verification control field and represents closing of the backend verification.
In the embodiment of the invention, the target check control field matched with the target rule check interface can be analyzed, and then the front-end check control field and the back-end check control field are determined, so that the field contents of the front-end check control field and the back-end check control field are respectively identified. If the front-end check control field is a front-end check opening field and the rear-end check control field is a rear-end check closing field, the front-end data to be checked in the data to be checked is checked according to the target check rule, the rear-end data to be checked in the data to be checked is checked according to the rear-end default check data, whether the front end and the rear end pass the same target check rule or not is controlled through setting the front-end check control field and the rear-end check control field, flexible check of the front end and the rear end aiming at the target check rule is achieved, and the client and the server can be controlled to check respectively.
Fig. 3 is a flow chart of processing online transaction data based on a rule engine according to a second embodiment of the present invention, as shown in fig. 3, before a client submits a page request (data submission request) to a server, the server may be preset, for example, rule configuration (configuration of target verification rule), switch configuration (configuration of target verification control field), rule interface configuration (configuration of target rule verification interface), and rule execution configuration are performed, and then the client sends a submit page request to the server to request an initial transaction interface (data input page), and the server submits a request page to the client, that is, returns the initial transaction interface, and renders a relevant page by the client. The rule execution configuration may include configuration of an execution order of the target check rule, and the like. After receiving the initial transaction interface, the client sends an asynchronous request rule file to the server so as to realize asynchronous call of the rule file based on the asynchronous request rule file. After receiving the asynchronous request rule file, the server processes the rule file in the rule engine to obtain a rule execution file comprising a target verification rule and a target verification control field, and sends the rule execution file to the client so that the client completes data verification. Specifically, the client obtains a front-end check control field according to the rule execution file, analyzes the front-end check control field, determines whether a client data check switch is turned on, if the client data check switch is turned on (the front-end check control field is a front-end check start field), checks front-end data to be checked according to a rule file execution form data general rule (a target check rule), checks front-end data to be checked according to a custom form data js (front-end default check data), and if the client data check switch is turned off, checks the front-end data to be checked according to the custom form data js. Wherein the js verification is the verification of the js programming language.
After the client completes data verification of the front-end data to be verified, a form request can be submitted to the server, so that the completed verification content can be fed back to the server through the form request. And after receiving the form request, the server executes the file according to the rule to check the data. Specifically, the server may analyze the backend verification control field to determine whether the server data verification switch is turned on, if the server data verification switch is turned on (the backend verification control field is the backend verification start field), verify the front-end data to be verified according to the rule file execution form data general rule (target verification rule), verify the backend data to be verified according to the custom server data (backend default verification data), and if the server data verification switch is turned off, verify the backend data to be verified according to the custom server data. After the server finishes the verification of the data to be verified at the back end, other processing of the server can be carried out, and the processing result is used as a target request page to be fed back to the client.
In the scheme, the client and the server can be subjected to double verification based on the same target verification rule, whether the server and the client are subjected to verification or not can be controlled through the verification switch, and whether the verification results are consistent or not is compared and checked. The rule engine where the target rule verification interface stored in the target verification rule is located is realized through JavaScript, each rule is also written by JavaScript, the target verification rule can be specifically stored in a database of the target rule verification interface, and the storage field of the target verification rule comprises a rule ID, a switch flag bit (target verification control field), a rule function, rule priority, data dependence and the like. The client and the server call the target verification rule through the target rule verification interface, the client verification (front-end verification) directly executes the target verification rule after acquiring the target verification rule through the target rule verification interface of the rule engine to obtain a verification result, the server verification (back-end verification) sends data to be verified, the rule ID and the like to the rule engine, the js engine in the rule engine executes the verification rule and then returns the verification result, and the client performs the rule verification in advance based on the same rule configuration before the server verification. While shielding invalid requests, malicious operation data submitted by bypassing client verification can be accurately positioned, and front and back end verification switch configuration is adopted, so that development and testing personnel can conveniently compare front and back end verification results and control a verification switch of specific transaction, namely, rule switches of different granularities such as an overall rule set or specific transaction can be controlled according to actual needs, and comparison of front and back end verification results and transaction customized rule configuration is facilitated.
Optionally, the rule engine may provide a unified rule writing specification and a unified rule configuration page, may add, modify, delete, and issue a rule, and may also perform rule configuration based on a service scenario and an interface request field. The rule engine provides a switch control function, and can control the on and off states of rule verification by modifying the switch flag bit of the specified rule of the database to determine whether the rule is executed or not. The related check results of the rule engine can be brought into a unified log platform and a risk transaction monitoring platform, and the abnormal check results are pushed to a related system.
According to the technical scheme of the embodiment, the data verification type matched with the data submission request is obtained in response to the data submission request, the target verification rule matched with the target rule verification interface is obtained, the data input page matched with the data submission request is fed back, the data to be verified is received through the data input page, and therefore the data to be verified is subjected to data verification matched with the data verification type by adopting the target verification rule. Because the data verification type matched with the data submission request comprises front-end verification, back-end verification and any one of the front-end verification and the back-end verification, the data to be verified can be flexibly selected according to actual verification requirements when the data to be verified is verified and matched with the data verification type, the problems that data verification behaviors of the front end and the back end are not controllable and user experience is poor in the prior art are solved, the data of the front end and the back end can be flexibly and controllably verified, and the user experience is improved.
It should be noted that any permutation and combination between the technical features in the above embodiments also belong to the scope of the present invention.
EXAMPLE III
Fig. 4 is a schematic diagram of a data verification apparatus according to a third embodiment of the present invention, and as shown in fig. 4, the apparatus includes: adata obtaining module 310, a to-be-verifieddata receiving module 320, and adata verifying module 330, wherein:
adata obtaining module 310, configured to, in response to the data submission request, obtain a data check type matching the data submission request, where the data check type includes: front end verification and/or back end verification;
thedata receiving module 320 to be verified is used for feeding back a data input page matched with the data submission request and receiving data to be verified through the data input page;
thedata verification module 330 is configured to perform data verification on the data to be verified, where the data verification type is matched with the data verification type.
According to the technical scheme of the embodiment, the data verification type which is matched with the data submission request and comprises front-end verification and/or back-end verification is obtained in response to the data submission request, the data input page matched with the data submission request is fed back, the data to be verified is received through the data input page, and therefore the data to be verified is subjected to data verification matched with the data verification type. Because the data verification type matched with the data submission request comprises front-end verification, back-end verification and any one of the front-end verification and the back-end verification, the data to be verified can be flexibly selected according to actual verification requirements when the data to be verified is verified and matched with the data verification type, the problems that data verification behaviors of the front end and the back end are not controllable and user experience is poor in the prior art are solved, the data of the front end and the back end can be flexibly and controllably verified, and the user experience is improved.
Optionally, thedata obtaining module 310 is specifically configured to identify a data submission type matched with the data submission request; acquiring the data submission type, and determining a target rule checking interface of a rule engine; acquiring a target verification control field matched with the target rule verification interface, wherein the target verification control field comprises a front-end verification control field and a rear-end verification control field; the front-end check control field and the back-end check control field are used for indicating the data check type.
Optionally, the data verification apparatus further includes a target verification rule obtaining module, configured to obtain a target verification rule matched with the target rule verification interface.
Optionally, thedata verification module 330 is specifically configured to perform data verification matching the data verification type on the data to be verified by using the target verification rule.
Optionally, thedata verification module 330 is specifically configured to, when it is determined that the front-end verification control field is a front-end verification start field and the back-end verification control field is a back-end verification start field, verify front-end data to be verified in the data to be verified according to the target verification rule, and verify back-end data to be verified in the data to be verified according to the target verification rule.
Optionally, the data verification apparatus further includes a first default data verification module, configured to obtain front-end default verification data, and verify, according to the front-end default verification data, front-end data to be verified in the data to be verified.
Optionally, the data verification apparatus further includes a second default data verification module, configured to acquire back-end default verification data, and verify the back-end data to be verified in the data to be verified according to the back-end default verification data.
Optionally, thedata verification module 330 is specifically configured to, when it is determined that the front-end verification control field is a front-end verification-off field and the back-end verification control field is a back-end verification-on field, verify front-end data to be verified in the data to be verified according to front-end default verification data, and verify back-end data to be verified in the data to be verified according to a target verification rule.
Optionally, thedata verification module 330 is specifically configured to, when it is determined that the front-end verification control field is a front-end verification start field and the back-end verification control field is a back-end verification close field, verify front-end data to be verified in the data to be verified according to a target verification rule, and verify back-end data to be verified in the data to be verified according to back-end default verification data.
The data verification device can execute the data verification method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method. For details of the technique not described in detail in this embodiment, reference may be made to the data verification method provided in any embodiment of the present invention.
Since the data verification apparatus described above is an apparatus capable of executing the data verification method in the embodiment of the present invention, based on the data verification method described in the embodiment of the present invention, a person skilled in the art can understand a specific implementation of the data verification apparatus in the embodiment and various variations thereof, and therefore, a detailed description of how the data verification apparatus implements the data verification method in the embodiment of the present invention is not provided here. The device used by those skilled in the art to implement the data verification method in the embodiments of the present invention is within the scope of the present application.
Example four
Fig. 5 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention. FIG. 5 illustrates a block diagram of anelectronic device 412 suitable for use in implementing embodiments of the present invention. Theelectronic device 412 shown in fig. 5 is only an example and should not bring any limitations to the functionality and scope of use of the embodiments of the present invention.
As shown in fig. 5, theelectronic device 412 is in the form of a general purpose computing device. The components of theelectronic device 412 may include, but are not limited to: one ormore processors 416, astorage device 428, and abus 418 that couples the various system components including thestorage device 428 and theprocessors 416.
Theelectronic device 412 may also communicate with one or more external devices 414 (e.g., keyboard, pointing device, camera,display 424, etc.), with one or more devices that enable a user to interact with theelectronic device 412, and/or with any devices (e.g., network card, modem, etc.) that enable theelectronic device 412 to communicate with one or more other computing devices. Such communication may be through an Input/Output (I/O)interface 422. Also, theelectronic device 412 may communicate with one or more networks (e.g., a Local Area Network (LAN), Wide Area Network (WAN), and/or a public Network, such as the internet) via theNetwork adapter 420. As shown,network adapter 420 communicates with the other modules ofelectronic device 412 overbus 418. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with theelectronic device 412, including but not limited to: microcode, device drivers, Redundant processing units, external disk drive Arrays, disk array (RAID) systems, tape drives, and data backup storage systems, to name a few.
Theprocessor 416 executes various functional applications and data processing by running programs stored in thestorage device 428, for example, implementing the data verification method provided by the above embodiments of the present invention, including: responding to the data submission request, and acquiring a data verification type matched with the data submission request, wherein the data verification type comprises: front end verification and/or back end verification; feeding back a data input page matched with the data submission request, and receiving data to be verified through the data input page; and carrying out data verification matched with the data verification type on the data to be verified.
According to the technical scheme of the embodiment, the data verification type which is matched with the data submission request and comprises front-end verification and/or back-end verification is obtained in response to the data submission request, the data input page matched with the data submission request is fed back, the data to be verified is received through the data input page, and therefore the data to be verified is subjected to data verification matched with the data verification type. Because the data verification type matched with the data submission request comprises front-end verification, back-end verification and any one of the front-end verification and the back-end verification, the data to be verified can be flexibly selected according to actual verification requirements when the data to be verified is verified and matched with the data verification type, the problems that data verification behaviors of the front end and the back end are not controllable and user experience is poor in the prior art are solved, the data of the front end and the back end can be flexibly and controllably verified, and the user experience is improved.
EXAMPLE five
An embodiment of the present invention further provides a computer storage medium storing a computer program, where the computer program is executed by a computer processor to perform the data verification method according to any one of the above embodiments of the present invention, and the computer program includes: responding to the data submission request, and acquiring a data verification type matched with the data submission request, wherein the data verification type comprises: front end verification and/or back end verification; feeding back a data input page matched with the data submission request, and receiving data to be verified through the data input page; and carrying out data verification matched with the data verification type on the data to be verified.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM) or flash Memory), an optical fiber, a portable compact disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, Radio Frequency (RF), etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. A method for data verification, comprising:
responding to a data submission request, and acquiring a data verification type matched with the data submission request, wherein the data verification type comprises: front end verification and/or back end verification;
feeding back a data input page matched with the data submission request, and receiving data to be verified through the data input page;
and performing data verification matched with the data verification type on the data to be verified.
2. The method of claim 1, wherein obtaining the data check type matching the data submission request comprises:
identifying a data submission type that matches the data submission request;
acquiring the data submission type, and determining a target rule checking interface of a rule engine;
acquiring a target verification control field matched with the target rule verification interface, wherein the target verification control field comprises a front-end verification control field and a rear-end verification control field;
the front-end check control field and the back-end check control field are used for indicating the data check type.
3. The method of claim 2, while obtaining the target check control field matching the target rule check interface, further comprising:
acquiring a target verification rule matched with the target rule verification interface;
and performing data verification matched with the data verification type on the data to be verified, wherein the data verification comprises the following steps:
and performing data verification matched with the data verification type on the data to be verified by adopting the target verification rule.
4. The method according to claim 3, wherein the performing, by using the target verification rule, data verification matching the data verification type for the data to be verified includes:
and when the front-end verification control field is determined to be a front-end verification opening field and the rear-end verification control field is determined to be a rear-end verification opening field, verifying front-end data to be verified in the data to be verified according to the target verification rule, and verifying rear-end data to be verified in the data to be verified according to the target verification rule.
5. The method according to claim 4, further comprising, after the verifying the front-end data to be verified in the data to be verified according to the target verification rule,:
acquiring front-end default verification data, and verifying the front-end data to be verified in the data to be verified according to the front-end default verification data;
after the verifying the back-end data to be verified in the data to be verified according to the target verification rule, the method further includes:
and acquiring back-end default verification data, and verifying back-end data to be verified in the data to be verified according to the back-end default verification data.
6. The method according to claim 3, wherein the performing, by using the target verification rule, data verification matching the data verification type for the data to be verified includes:
when the front-end verification control field is determined to be a front-end verification closing field and the rear-end verification control field is determined to be a rear-end verification opening field, front-end data to be verified in the data to be verified are verified according to front-end default verification data, and rear-end data to be verified in the data to be verified are verified according to a target verification rule.
7. The method according to claim 3, wherein the performing, by using the target verification rule, data verification matching the data verification type for the data to be verified includes:
when the front-end verification control field is determined to be a front-end verification opening field and the rear-end verification control field is determined to be a rear-end verification closing field, front-end data to be verified in the data to be verified are verified according to a target verification rule, and rear-end data to be verified in the data to be verified are verified according to rear-end default verification data.
8. A data verification apparatus, comprising:
the data acquisition module is used for responding to a data submission request and acquiring a data verification type matched with the data submission request, wherein the data verification type comprises: front end verification and/or back end verification;
the data receiving module to be verified is used for feeding back a data input page matched with the data submitting request and receiving data to be verified through the data input page;
and the data verification module is used for performing data verification matched with the data verification type on the data to be verified.
9. An electronic device, characterized in that the electronic device comprises:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement a data verification method as claimed in any one of claims 1-7.
10. A computer storage medium on which a computer program is stored, which program, when being executed by a processor, carries out the data verification method as claimed in any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210175849.7ACN114564353A (en) | 2022-02-25 | 2022-02-25 | Data verification method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210175849.7ACN114564353A (en) | 2022-02-25 | 2022-02-25 | Data verification method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114564353Atrue CN114564353A (en) | 2022-05-31 |
Family
ID=81716361
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210175849.7APendingCN114564353A (en) | 2022-02-25 | 2022-02-25 | Data verification method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114564353A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115146322A (en)* | 2022-09-01 | 2022-10-04 | 杭州安恒信息技术股份有限公司 | A data verification method, device, equipment and storage medium |
- 2022
- 2022-02-25CNCN202210175849.7Apatent/CN114564353A/enactivePending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115146322A (en)* | 2022-09-01 | 2022-10-04 | 杭州安恒信息技术股份有限公司 | A data verification method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111598122B (en) | Data verification method and device, electronic equipment and storage medium | |
| CN111416811A (en) | Unauthorized vulnerability detection method, system, equipment and storage medium | |
| CN107145440B (en) | Application program testing method and device and computer equipment | |
| CN109815147B (en) | Test case generation method, device, server and medium | |
| CN109871315B (en) | Diagnosis method and device for system upgrade failure based on machine learning | |
| CN112685029A (en) | Visual template generation method, device, equipment and storage medium | |
| CN110109824B (en) | Big data autoregression test method and device, computer equipment and storage medium | |
| CN113704102B (en) | Application program compliance detection method, device, equipment and medium | |
| CN109684008B (en) | Card rendering method, device, terminal and computer readable storage medium | |
| CN110471728B (en) | Method and related device for displaying interface based on user permission | |
| US20220301564A1 (en) | Method for executing instruction, relevant apparatus and computer program product | |
| CN113032834A (en) | Database table processing method, device, equipment and storage medium | |
| CN111741046B (en) | Data reporting method, data acquisition method, device, equipment and medium | |
| CN115080433A (en) | Testing method and device based on flow playback | |
| CN110134869B (en) | Information pushing method, device, equipment and storage medium | |
| CN113362173B (en) | Anti-duplicate mechanism verification method, verification system, electronic device and storage medium | |
| CN113157699B (en) | Business data auditing method and device and electronic equipment | |
| US20120054724A1 (en) | Incremental static analysis | |
| CN110717315B (en) | System data batch modification method and device, storage medium and electronic equipment | |
| CN112926059A (en) | Data processing method, device, equipment and storage medium | |
| US20120198555A1 (en) | Testing web services that are accessible via service oriented architecture (soa) interceptors | |
| CN114564353A (en) | Data verification method and device, electronic equipment and storage medium | |
| CN113901773B (en) | Data accounting method, device, electronic equipment and storage medium | |
| CN110674491B (en) | Method and device for real-time evidence obtaining of android application and electronic equipment | |
| CN113870969A (en) | Health assessment report generation method, system, server and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |