CN107203714B - Configuration method and device of data verification file - Google Patents
Configuration method and device of data verification file Download PDFInfo
- Publication number
- CN107203714B CN107203714B CN201610159287.1A CN201610159287A CN107203714B CN 107203714 B CN107203714 B CN 107203714B CN 201610159287 A CN201610159287 A CN 201610159287A CN 107203714 B CN107203714 B CN 107203714B
- Authority
- CN
- China
- Prior art keywords
- data verification
- new version
- file
- mode information
- data
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/45—Structures or tools for the administration of authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2133—Verifying human interaction, e.g., Captcha
Abstract
The application discloses a configuration method and device of a data verification file. One embodiment of the method comprises: acquiring a data verification configuration file and a verification file of a new version, wherein the data verification configuration file is loaded with data verification mode information of an old version; analyzing the new version of the check file to obtain the new version of the data check mode information; and loading the data verification mode information of the new version in the data verification configuration file to replace the data verification mode information of the old version and update the data verification configuration file. The implementation mode realizes the dynamic configuration and the dynamic loading of the data verification mode information, can realize the updating of the data verification mode information without restarting a program, and improves the stability of the system.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to the field of data processing, and in particular, to a method and an apparatus for configuring a data verification file.
Background
Data verification is a technology for verifying input data in order to ensure the integrity, correctness and security of data, and is an important means for system and user data security in the internet technology. Most of existing data verification frameworks are configured based on data verification files, and when a program which needs to verify input data is started, data verification mode information is initialized. Because the data verification mode information is integrated in the data verification file, when the data verification mode information in the program needs to be changed, the program needs to be restarted after the data verification file is reconfigured, and the new data verification mode information can take effect. In this way, the real-time performance of the data verification mode information change is poor, which may affect the operation quality of the system and is not favorable for the high availability of the system.
Disclosure of Invention
In view of the above, it is desirable to provide a configuration method for a data check file that is good in real-time performance and does not require a restart program, and further, it is desirable to provide a configuration method for a data check file that separates data check mode information from a data check file so that data check logic can be dynamically loaded when data is checked. In order to solve one or more of the above problems, the present application provides a configuration method and apparatus for a data check file.
In one aspect, the present application provides a method for configuring a data check file, including: acquiring a data verification configuration file and a verification file of a new version, wherein the data verification configuration file is loaded with data verification mode information of an old version; analyzing the new version of the check file to obtain the new version of the data check mode information; and loading the data verification mode information of the new version in the data verification configuration file to replace the data verification mode information of the old version and update the data verification configuration file.
In some optional implementation manners, the data verification configuration file includes a call interface of data verification manner information, and the loading of the new version of the data verification manner information in the data verification configuration file includes: detecting whether the data verification mode information of the new version exists or not; and calling the data verification mode information of the new version through a calling interface of the data verification mode information in response to the fact that the data verification mode information of the new version exists.
In some optional implementations, the parsing the new version of the check file to obtain the new version of the check mode includes: identifying configuration information in the new version of the check file; and extracting configuration information corresponding to the verification mode of the new version.
In some optional implementations, the loading the new version of data verification manner information in the data verification configuration file includes: judging whether the data verification mode information of the new version contains script keywords or not; if so, calling the data verification mode information of the new version by adopting a configured script engine; wherein the script engine is configured based on the script key.
In some optional implementations, the method further comprises: and generating the new version of the verification file based on the updating configuration operation of the user on the data verification mode information.
In a second aspect, the present application provides a configuration apparatus for a data check file, including: the device comprises an acquisition unit, a verification unit and a verification unit, wherein the acquisition unit is used for acquiring a data verification configuration file and a new version of verification file, and the data verification configuration file is loaded with old version of data verification mode information; the analysis unit is used for analyzing the new version of the check file to obtain the new version of the data check mode information; and a loading unit, configured to load the new version of data verification mode information in the data verification configuration file to replace the old version of data verification mode information and update the data verification configuration file.
In some optional implementation manners, the data verification configuration file includes a call interface of data verification manner information, and the loading unit includes: the detection module is used for detecting whether the data verification mode information of the new version exists or not; and the calling module is used for calling the data verification mode information of the new version through a calling interface of the data verification mode information in response to the fact that the data verification mode information of the new version exists.
In some optional implementations, the loading unit is further configured to load the data verification mode information of the new version as follows: judging whether the new version of the data verification file contains script keywords or not; if so, calling the data verification mode information of the new version by adopting a configured script engine; wherein the script engine is configured based on the script key.
In some optional implementations, the apparatus further comprises: and the generating unit is used for generating the new version of the verification file based on the updating configuration operation of the user on the data verification mode information.
According to the configuration method and device for the data verification file, the data verification configuration file and the new version of the verification file are obtained, then the new version of the verification file is analyzed to obtain the data verification mode information of the new version, and finally the data verification mode information of the new version is loaded in the data verification configuration file, so that the data verification mode information of the old version is replaced and the data verification configuration file is updated, dynamic configuration and dynamic loading of the data verification mode information are achieved, updating of the data verification mode information can be achieved without restarting a program, real-time effect of the new data verification mode information is guaranteed, and the operation quality of a system is improved.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, with reference to the accompanying drawings in which:
FIG. 1 is an exemplary system architecture diagram in which the present application may be applied.
FIG. 2 is a flow diagram of one embodiment of a method for configuring a data verification file according to the present application.
FIG. 3 is a schematic diagram illustrating an effect of a scenario in which the configuration method of the data verification file of the present application may be applied;
FIG. 4 is a flow diagram of another embodiment of a method for configuring a data verification file according to the present application;
FIG. 5 is a flow diagram of a specific implementation of the embodiment shown in FIG. 4;
FIG. 6 is a schematic block diagram illustrating one embodiment of a configuration apparatus for a data verification file according to the present application;
fig. 7 is a schematic structural diagram of a computer system suitable for implementing the terminal device or the server according to the embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Reference is made to fig. 1, which illustrates an exemplary system architecture diagram to which the present application may be applied. As shown in fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user 110 may use the terminal devices 101, 102, 103 to interact with the server 105 over the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have various web services applications installed thereon, such as a web browser application, an online shopping application, a search application, an instant messaging tool, a mailbox client, social platform software, an online audio/video playing application, and the like. In the application of the present application, a user 110 uses an application on a device 101, 102, 103 to make a request for a network service to a server 105 and to receive data relating to the requested network service from the server 105.
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting user operations, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture experts Group Audio Layer III, motion Picture experts compression standard Audio Layer 3), MP4 players (Moving Picture experts Group Audio Layer IV, motion Picture experts compression standard Audio Layer 4), laptop portable computers, desktop computers, and the like.
The server 105 may be a server providing various services, such as a background data server providing data support for network requests issued by the terminal devices 101, 102, 103. The background data server may parse the received network request and verify the security of the network request (e.g., verify whether the login name and the password of the user match), and then feed back the processing result to the terminal device.
It should be noted that the configuration method of the data verification file provided in the embodiment of the present application may be executed by the terminal device 101, 102, 103 or the server 105, and accordingly, the configuration device of the data verification file is generally disposed in the terminal device 101, 102, 103 or the server 105.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring to fig. 2, a flowchart of an embodiment of a configuration method of a data check file according to the present application is shown. As shown in fig. 2, the process 200 of the configuration method of the data check file includes the following steps:
In this embodiment, the electronic device on which the configuration method for the data verification file is executed may obtain the existing data verification configuration file and the new version of the verification file in the memory. And the data verification configuration file is loaded with the data verification mode information of the old version. Specifically, the data verification configuration file may include configuration information of the data verification, such as data verification rule information, storage addresses of related parameters of the data verification, and the like. The data verification rule information may include data verification mode information of an old version.
The verification file may be a script file or a JSON (JavaScript object notation) file containing data verification mode information, and in an actual scene, the verification file may contain data verification logic, such as a function, a parameter, a data operation command, and the like called when data is verified.
In this embodiment, if the data verification mode information of the system needs to be changed, the entire data verification configuration file does not need to be modified, only a new version of the verification file including new verification logic may be configured, and after the configuration is completed, the new version of the verification file may be stored in a memory of the electronic device on which the configuration method of the data verification file is executed, or may be stored on the cloud server. When the data verification file is configured, the electronic device can read the data verification file from the memory or request the new version of the verification file from the cloud server.
When a user starts or enters an application, data can be sent to the application, and the background of the application can verify the data sent by the user. The checking mode can be changed according to the application requirement or the scene. And generating a new version of check file after the data check mode information is changed. An exemplary scenario is: when a user enters a shopping-like client application, login data, such as a username, password, authentication code, etc., may be submitted to the application's server. The memory of the server of the application can store a data verification configuration file for verifying the login data submitted by the user. The data verification configuration file contains data verification rules (e.g., scripts for implementing verification algorithms). The server of the shopping client application can verify the login data submitted by the user according to the data verification configuration file, and determine whether the data can be returned to the user according to the verification result. When a background maintainer of the shopping client application changes the data verification algorithm, a new version of verification file containing the new data verification algorithm can be generated, and the server can verify login data submitted by a user based on data verification mode information in the new version of verification file.
In this embodiment, the electronic device may identify the acquired new version of the verification file, so as to determine the input data corresponding to the new version of the verification file. For example, when the input data includes more than two items, if only one item of data verification mode information is changed, the new version of verification file only contains the new verification logic of the item of data. When the data verification file is configured, the electronic device can identify corresponding data from the new verification logic, so that only the verification mode of the data is updated in the data verification file, and the verification modes of other data are not changed.
The new version of the check file may include the new version of the data check mode information and configuration information related to the new version of the data check mode information. For example, the type of entry of the new version of data verification mode information, the type of exit of the new version of data verification mode information, the internal logic of the called function, the storage address of the relevant parameter, and the like can be included. In this embodiment, the electronic device may analyze the new version of the data verification method information from the new version of the data verification method information. Further, the configuration information in the new version of the verification file can be identified, the configuration information corresponding to the verification mode of the new version is extracted, and then the verification mode of the new version can be identified according to the configuration information. Specifically, the configuration information may be identified according to a specific identifier in each configuration information, for example, the configuration information may be identified as an entry type or an exit type according to an "int" character in one piece of configuration information.
After the new version of the data verification mode information is analyzed, the new version of the data verification mode information can be loaded in the data verification configuration file, so that the data verification configuration file is updated. After the new version of the data verification mode information is loaded, the input data can be verified according to the updated data verification configuration file. Specifically, when the verification mode is called, the new version of data verification mode information can be called through the data verification configuration file to verify the input data.
In some optional implementation manners of this embodiment, the data verification configuration file acquired in step 201 may include a call interface of the data verification manner information, and the new version of the data verification manner information may be loaded in the following manner: and detecting whether the new version of data verification mode information exists, and calling the new version of data verification mode information through the calling interface of the data verification mode information in response to the detection that the new version of data verification mode information exists. The electronic equipment can determine whether the new version of data verification mode information exists by detecting whether the new version of verification file exists. For example, whether a keyword of a new version of the check file exists or not may be detected, and if the keyword is detected, it may be determined that the new version of the data check mode information exists. When the new version of data verification mode information is detected to exist, the new version of data verification mode information can be called through a calling interface of the data verification mode information in the data verification configuration file.
In some optional implementation manners of this implementation, the flow 200 of the configuration method for the data check file may further include: and generating a new version of the verification file based on the updating configuration operation of the user on the data verification mode information. When the verification rule of the application or system changes, a user can update and configure the data verification mode information of the new version in the background server of the application or the electronic device on which the application runs, and update the data verification rule, and the electronic device can generate new verification logic in response to the update operation of the user and generate a verification file of the new version based on the new verification logic. The updating of the data verification rules may include updating of parameter ranges and updating of verification methods. The user can modify the value range of the parameter related to the data to be verified in the background, and also can modify the algorithm or the called function name adopted in verification, thereby updating the data verification rule.
In this embodiment, the check file including the data check logic may be separated from the data check configuration file, and when the data check mode information needs to be changed, only the check file may be modified to generate a new version of the check file. The problem of system operation quality reduction caused by the fact that the whole data check file needs to be modified and the system needs to be restarted when the check mode is changed in the prior art is solved, and support is provided for high availability of the system.
Further referring to fig. 3, it shows an effect diagram of a scenario to which the configuration method of the data check file of the present application may be applied. As shown in FIG. 3, before the data verification mode information is updated, the system configures the length of the password to be 6-18, and when the user1 inputs the password with 4 bits, the system prompts that the password length is 6-18 bits, and the user1 cannot log in successfully. At this time, if the configuration of the password length is modified at the background to 4-18 bits and a new verification file is generated, when another user2 logs in, if a 4-bit password is also input, the system can load the new verification file, and judge that the user2 passes the data verification according to the new verification configuration, and prompt information related to the data verification rule does not pop up in the login interface. In the process, the system does not need to be restarted or the application does not need to be restarted between the login operations of the user1 and the user2, the new data verification rule takes effect in real time in the background, and the system friendliness is improved.
With continuing reference to FIG. 4, a flow diagram of another embodiment of a method for configuration of a data check file according to the present application is shown. As shown in fig. 4, the process 400 of the configuration method of the data check file includes the following steps:
In this embodiment, the electronic device on which the configuration method for the data check file operates may obtain the existing data check configuration file and the new version check file in the memory, and may also send a request to other electronic devices, and then receive the data check configuration file and the new version check file sent by other electronic devices in response to the request. And the data verification configuration file is loaded with the data verification mode information of the old version. Specifically, the data verification configuration file may include configuration information of the data verification, such as data verification rule information, storage addresses of related parameters of the data verification, and the like. The data verification rule information may include data verification mode information of an old version.
In an actual scenario, the check file may include data check logic, for example, a function, a parameter, a data operation command, and the like that are called when the data is checked.
When a user starts or enters an application, data can be sent to the application, and the background of the application can verify the data sent by the user. The checking mode can be changed according to the application requirement or the scene. And generating a new version of check file after the data check mode information is changed. The new version of the check file can be saved in the server of the application and can also be released to the public platform of the application to inform the user entering the application that the data check mode information is updated.
The new version of the check file may include the new version of the data check mode information and configuration information related to the new version of the data check mode information. For example, the type of entry of the new version of data verification mode information, the type of exit of the new version of data verification mode information, the internal logic of the called function, the storage address of the relevant parameter, and the like can be included. In this embodiment, the electronic device may identify the acquired new version of the check file to analyze the new version of the data check mode information. Further, the configuration information in the new version of the verification file can be identified, the configuration information corresponding to the verification mode of the new version is extracted, and then the verification mode of the new version can be identified according to the configuration information. Specifically, the configuration information may be identified according to a specific identifier in each configuration information, for example, the configuration information may be identified as an entry type or an exit type according to an "int" character in one piece of configuration information.
The new version of data verification means information may include updated data verification logic. In this embodiment, if the updated data verification logic is implemented by a Java-based scripting language, the data verification mode information may include a script keyword, such as "< script >", "var", and the like. And if the electronic equipment detects the script keyword, determining that the verification file of the new version is the script file. In practical application, a script keyword library containing a plurality of script keywords can be established, and if the keywords in the script keyword library exist in the data verification mode information of the new version, the new version of the verification file can be determined to be the script file. Further, if the data verification mode information does not include the script keyword, it may be determined that the new version of the verification file is not a script file.
And step 404, if yes, calling the data verification mode information of the new version by using the configured script engine.
If it is determined in step 403 that the new version of data verification method information includes the script keyword, the new version of data verification method information may be invoked based on the configured script engine. For example, the updated data verification configuration file may be analyzed by an analysis engine based on JavaScript, and in this process, the JavaScript analysis engine may automatically invoke the data verification mode information of the new version through the invocation interface, and run the updated data verification configuration file. Specifically, the JavaScript parsing engine may be a framework required for running the data verification configuration file, and provides a code for running the data verification configuration file.
The script engine may be configured in advance based on a script keyword. Different script keywords correspond to different script engines. Optionally, the electronic device may store a script engine dictionary including a corresponding relationship between a script keyword and a script engine, and when the new version of data verification mode information is called, the script engine dictionary may be searched for a corresponding script engine according to the keyword, and the new version of data verification mode information is called by the searched script engine.
In some optional implementation manners of this embodiment, if the determination result in step 403 is negative, that is, the new version of data verification manner information does not include a script keyword, it may be determined that the new version of verification file is not a script file, and at this time, the new version of data verification manner may be loaded based on a built-in developed parsing framework.
In some optional implementation manners of this embodiment, before step 404, the process 400 of configuring the data check file may further include: and if so, generating a corresponding script engine based on the script keyword so that the data verification configuration file adopts the script engine to call the data verification mode information of the new version. Further, before step 404, the method flow 400 may further include, if not, generating an analysis template based on a built-in analysis framework, so that the data verification configuration file calls new version data verification mode information based on the analysis template.
With further reference to fig. 5, a flow chart of a specific implementation of the embodiment shown in fig. 4 is shown. As shown in fig. 5, when configuring the data check file, the check file is loaded first, and the check file may be a new version check mode file stored in the cloud or locally, which includes a new version check logic. Optionally, when the check file is loaded, the check file may be parsed, and check logic therein may be extracted. Meanwhile, whether the script key words exist in the verification file or not can be judged, if yes, a corresponding script engine can be generated, and the script engine is called for verification when data are verified; if not, an analysis template can be generated based on a built-in analysis framework, so that verification is performed based on the analysis template during data verification, and finally the data verification configuration file is updated. In practical application, when the script key word exists in the verification file, the verification logic in the verification file can be directly analyzed by using the script engine in the data verification configuration file, and when the script key word does not exist in the verification file, the verification logic in the verification file can be loaded by calling the analysis template, so that a new data verification mode can take effect when new data is input next time. Therefore, the new verification mode can be enabled to take effect without restarting the program, and the stability of the system is improved.
Compared with the embodiment shown in fig. 2, the embodiment shown in fig. 4 highlights the step of loading the new version of data verification mode information, further details the steps of the method, and provides a fast and real-time configuration method of the data verification file for the scenario of the script file for the new version of the verification file.
With further reference to FIG. 6, a block diagram of one embodiment of a configuration device for a data check file according to the present application is shown. As shown in fig. 6, the configuration apparatus 600 for a data check file includes: an acquisition unit 601, a parsing unit 602, and a loading unit 603. The obtaining unit 601 is configured to obtain a data verification configuration file and a new version of verification file by a back-end driver, where the data verification configuration file is loaded with an old version of data verification mode information; the parsing unit 602 is configured to parse the new version of the check file to obtain new version of data check mode information; the loading unit 603 is configured to load the new version of the data verification mode information in the data verification configuration file, so as to replace the old version of the data verification mode information and update the data verification configuration file.
In this embodiment, the obtaining unit 601 may obtain the data verification configuration file and the new version verification file from the cloud or the local. The data verification configuration file may include configuration information of data verification, such as data verification rule information, storage addresses of related parameters of data verification, and the like. The data verification rule information may include data verification mode information of an old version. The verification file may be a script file or a JSON (JavaScript object Notation) file containing data verification mode information, and in an actual scene, the verification file may contain data verification logic, for example, a function, a parameter, a data operation command, and the like called when data is verified.
The parsing unit 602 may identify the acquired new version check file, so as to determine input data corresponding to the new version check file. For example, when the input data includes more than two items, if only one item of data verification mode information is changed, the new version of verification file only contains the new verification logic of the item of data. When configuring the data check file, the parsing unit 602 may identify corresponding data from the new check logic, so that only the check mode of the data is updated in the data check file, and the check modes of other data are not changed.
In some optional implementation manners of this embodiment, the parsing unit 602 may parse the new version of the data verification manner information from the new version of the data verification manner information. Further, the parsing unit 602 may include an identification module and an extraction module, where the identification module may identify the configuration information in the new version of the check file, and the extraction module may extract the configuration information corresponding to the new version of the check mode, and then may identify the new version of the check mode according to the configuration information. Specifically, the configuration information may be identified according to a specific identifier in each configuration information, for example, the configuration information may be identified as an entry type or an exit type according to an "int" character in one piece of configuration information.
After the parsing unit 602 parses the new version of the data verification manner information, the loading unit 603 may load the new version of the data verification manner information in the data verification configuration file, so as to update the data verification configuration file. After the new version of the data verification mode information is loaded, the input data can be verified according to the updated data verification configuration file. Specifically, when the verification mode information is called, the new version of the data verification mode information can be called through the data verification configuration file to verify the input data.
In some optional implementation manners of this embodiment, the data verification configuration file acquired by the acquiring unit 601 may include a call interface of the data verification manner information, and the loading unit 603 may load the new version of the data verification manner information in the following manner: and detecting whether the new version of data verification mode information exists, and calling the new version of data verification mode information through the calling interface of the data verification mode information in response to the detection that the new version of data verification mode information exists. Further, the loading unit 603 may further load the new version of the data verification method information by: judging whether the data verification file of the new version contains script keywords or not; and if so, calling the data verification mode information of the new version by adopting the configured script engine. Wherein the script engine is configured based on the script key.
In some optional implementations of this implementation, the apparatus 600 may further include a generating unit (not shown). The generating unit may be configured to generate a new version of the verification file based on an update configuration operation of the user on the data verification manner information. After a new version of the verification file is generated, the bankroll 600 may configure the data verification file, and when input data to be verified is detected, the updated data verification file is used for verification without restarting a system or a program in the configuration process.
Those skilled in the art will appreciate that the above-described configuration means 600 for the data check file may also include some other well-known structures, such as a processor, memory, etc., which are not shown in fig. 6 in order to not unnecessarily obscure embodiments of the present disclosure.
The configuration apparatus 600 for data verification files provided in the above embodiment of the present application separates the verification file from the data verification configuration file, and when the verification rule is changed, only the verification file may be modified, and the new version of the verification file is released, so that the apparatus 600 may automatically obtain and analyze the new version of the verification file. When data verification is carried out, the data verification mode information in the new version of the verification file can be automatically called for verification, and the verification file can take effect without restarting a program or the new verification mode information of the system. The dynamic configuration of the data verification file is realized, and the stability of system operation is improved.
Referring now to FIG. 7, shown is a block diagram of a computer system 700 suitable for use in implementing a terminal device or server of an embodiment of the present application.
As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU)701, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data necessary for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes an acquisition unit, a parsing unit, and a loading unit. The names of these units do not form a limitation to the unit itself in some cases, and for example, the obtaining unit may also be described as a "unit for obtaining a data verification configuration file and a new version of a verification file".
As another aspect, the present application also provides a non-volatile computer storage medium, which may be the non-volatile computer storage medium included in the apparatus in the above-described embodiments; or it may be a non-volatile computer storage medium that exists separately and is not incorporated into the terminal. The non-transitory computer storage medium stores one or more programs that, when executed by a device, cause the device to: acquiring a data verification configuration file and a verification file of a new version, wherein the data verification configuration file is loaded with data verification mode information of an old version; analyzing the new version of the check file to obtain the new version of the data check mode information; and loading the data verification mode information of the new version in the data verification configuration file to replace the data verification mode information of the old version and update the data verification configuration file.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by a person skilled in the art that the scope of the invention as referred to in the present application is not limited to the embodiments with a specific combination of the above-mentioned features, but also covers other embodiments with any combination of the above-mentioned features or their equivalents without departing from the inventive concept. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (10)
1. A configuration method of a data check file is characterized by comprising the following steps:
acquiring a data verification configuration file and a new version of verification file, wherein the data verification configuration file is loaded with old version of data verification mode information and comprises a calling interface of the data verification mode information;
analyzing the new version of the check file to obtain the new version of the data check mode information; and
loading the data verification mode information of the new version in the data verification configuration file to replace the data verification mode information of the old version and update the data verification configuration file;
wherein, the loading the data verification mode information of the new version in the data verification configuration file includes:
detecting whether the data verification mode information of the new version exists or not;
and calling the data verification mode information of the new version through a calling interface of the data verification mode information in response to the fact that the data verification mode information of the new version exists.
2. The method of claim 1, wherein parsing the new version of the check file to obtain the new version of the check mode comprises:
identifying configuration information in the new version of the check file;
and extracting configuration information corresponding to the verification mode of the new version.
3. The method of claim 1, wherein the loading the new version of data verification manner information in the data verification configuration file comprises:
judging whether the data verification mode information of the new version contains script keywords or not;
if so, calling the data verification mode information of the new version by adopting a configured script engine;
wherein the script engine is configured based on the script key.
4. The method according to any one of claims 1-3, further comprising:
and generating the new version of the verification file based on the updating configuration operation of the user on the data verification mode information.
5. A device for configuring a data check file, comprising:
the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a data verification configuration file and a new version of verification file, the data verification configuration file is loaded with old version of data verification mode information, and the data verification configuration file comprises a calling interface of the data verification mode information;
the analysis unit is used for analyzing the new version of the check file to obtain the new version of the data check mode information; and
a loading unit, configured to load the new version of data verification mode information in the data verification configuration file to replace the old version of data verification mode information and update the data verification configuration file;
wherein the loading unit includes:
the detection module is used for detecting whether the data verification mode information of the new version exists or not;
and the calling module is used for calling the data verification mode information of the new version through a calling interface of the data verification mode information in response to the fact that the data verification mode information of the new version exists.
6. The apparatus of claim 5, wherein the parsing unit comprises:
the identification module is used for identifying the configuration information in the new version of the check file;
and the extraction module extracts the configuration information corresponding to the verification mode of the new version.
7. The apparatus of claim 5, wherein the loading unit is further configured to load the new version of data verification mode information as follows:
judging whether the new version of the data verification file contains script keywords or not;
if so, calling the data verification mode information of the new version by adopting a configured script engine;
wherein the script engine is configured based on the script key.
8. The apparatus of any of claims 5-7, further comprising:
and the generating unit is used for generating the new version of the verification file based on the updating configuration operation of the user on the data verification mode information.
9. An apparatus, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-4.
10. A computer-readable storage medium, on which a computer program is stored, wherein the program, when executed by a processor, implements the method of any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610159287.1A CN107203714B (en) | 2016-03-18 | 2016-03-18 | Configuration method and device of data verification file |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610159287.1A CN107203714B (en) | 2016-03-18 | 2016-03-18 | Configuration method and device of data verification file |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107203714A CN107203714A (en) | 2017-09-26 |
| CN107203714B true CN107203714B (en) | 2020-09-01 |
Family
ID=59904469
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610159287.1A Active CN107203714B (en) | 2016-03-18 | 2016-03-18 | Configuration method and device of data verification file |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107203714B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107861832B (en) * | 2017-09-27 | 2020-11-13 | 深信服科技股份有限公司 | Data verification method and device and readable storage medium |
| CN113259320A (en) * | 2021-04-12 | 2021-08-13 | 顶象科技有限公司 | Verification mode dynamic installation method, system, electronic device and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101021890A (en) * | 2007-03-20 | 2007-08-22 | 华为技术有限公司 | Method, system and server for checking page data |
| CN104104701A (en) * | 2013-04-08 | 2014-10-15 | 腾讯科技（深圳）有限公司 | Online service configuration updating method and system |
| CN104199666A (en) * | 2014-09-09 | 2014-12-10 | 北京京东尚科信息技术有限公司 | Dynamic configuration method and device for application program |
| CN106598633A (en) * | 2015-10-19 | 2017-04-26 | 北京国双科技有限公司 | Configuration file update method, client and server |
-
2016
- 2016-03-18 CN CN201610159287.1A patent/CN107203714B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101021890A (en) * | 2007-03-20 | 2007-08-22 | 华为技术有限公司 | Method, system and server for checking page data |
| CN104104701A (en) * | 2013-04-08 | 2014-10-15 | 腾讯科技（深圳）有限公司 | Online service configuration updating method and system |
| CN104199666A (en) * | 2014-09-09 | 2014-12-10 | 北京京东尚科信息技术有限公司 | Dynamic configuration method and device for application program |
| CN106598633A (en) * | 2015-10-19 | 2017-04-26 | 北京国双科技有限公司 | Configuration file update method, client and server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107203714A (en) | 2017-09-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110602052B (en) | Micro-service processing method and server | |
| US8819630B2 (en) | Automatic test tool for webpage design with micro-browsers on mobile platforms | |
| US9984215B2 (en) | Obtaining password data | |
| KR20110030461A (en) | System and method for dynamic partitioning of applications in client-server environments | |
| US10592399B2 (en) | Testing web applications using clusters | |
| US10621651B2 (en) | Automatic recharge system and method, and server | |
| KR20160085276A (en) | Method, device, and system for updating authentication informatoin | |
| CN105791249A (en) | Third-party application processing method, device and system | |
| CN106021319A (en) | Voice interaction method, device and system | |
| CN107203714B (en) | Configuration method and device of data verification file | |
| CN115396180A (en) | Micro service gateway unified authentication method, device, micro service gateway and storage medium | |
| CN107402878B (en) | Test method and device | |
| CN114385382A (en) | Light application access method and device, computer equipment and storage medium | |
| CN112231696A (en) | Malicious sample identification method and device, computing equipment and medium | |
| US20160127445A1 (en) | Methods and devices for identifying terminal | |
| CN113760274B (en) | Front-end assembly logic injection method and device | |
| CN107357562A (en) | A kind of information fill method, device and client | |
| CN112527802B (en) | Soft link method and device based on key value database | |
| CN112579428A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN114465811B (en) | Website login determination method and device, electronic equipment and storage medium | |
| CN113688152B (en) | System function self-checking method and device | |
| CN111885006B (en) | Page access and authorized access method and device | |
| CN113297087A (en) | Test method and device | |
| CN113900652A (en) | Automatic conversion method, device, equipment, medium and product of comparison test script | |
| CN113393318A (en) | Bank card application wind control method and device, electronic equipment 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |