CN114900546B - Data processing method, device and equipment and readable storage medium - Google Patents
Data processing method, device and equipment and readable storage medium Download PDFInfo
- Publication number
- CN114900546B CN114900546B CN202210801014.8A CN202210801014A CN114900546B CN 114900546 B CN114900546 B CN 114900546B CN 202210801014 A CN202210801014 A CN 202210801014A CN 114900546 B CN114900546 B CN 114900546B
- Authority
- CN
- China
- Prior art keywords
- target
- service request
- routing table
- path
- rule information
- 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
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/745—Address table lookup; Address filtering
Abstract
The specification discloses a data processing method, a data processing device, a data processing apparatus and a readable storage medium, wherein a target variable contained in each path rule information in a routing table is updated to a wildcard regular expression in a manner of constructing a target routing table, and a corresponding relation between the path rule information corresponding to each service request containing the wildcard regular expression and a method for a controller layer to process each service request call is constructed. Therefore, the target variables in the route rule information of the routing table are updated to the wildcard regular expression, the route rule information matched with the URL route information carried by the received target service request in the target routing table can be accurately inquired, the method called by the controller layer for processing the target service request is further accurately obtained, and the efficiency of executing the service based on the URL is improved.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a data processing method, an apparatus, a device, and a readable storage medium.
Background
With the development of internet technology, the use of various different types of pages developed through a platform application development framework is also more and more widespread. During service execution, a user may send a service request carrying a Uniform Resource Locator (URL), so that a service execution party executes a service. And the service executing party determines a method called by the controller layer for processing the service corresponding to the URL according to the URL, and further executes the service corresponding to the URL according to the determined method. However, in practical applications, the path information of the URL carried by the service request is determined according to preset path rule information and a dynamic variable, where the preset path rule information and the method called by the controller layer have a corresponding relationship. Thus, it may happen that services corresponding to different URLs can call the same method for processing. Therefore, the service executing party can perform URL normalization processing on similar URL data to determine that the same method URL is called so as to execute the service efficiently.
In the prior art, URL normalization processing is usually performed on URLs according to preset rules to obtain URL normalization processing results, for example, URL normalization processing is performed according to manually written URL normalization rules, or URL normalization processing is performed according to similarity degrees among URLs, and the like. And according to the URL normalization processing result, all URLs with the same URL normalization processing result are regarded as URLs needing to call the same method, the same processing means are adopted to unify path information, and the service is executed.
However, the above method still depends on manual experience (e.g., rule formulation or setting of similarity threshold), and the URL normalization processing of URLs requiring different methods may be performed to obtain the same URL normalization processing result, which affects the efficiency of executing the service.
Based on this, this specification provides a data processing method based on a safe tangent plane.
Disclosure of Invention
The present specification provides a data processing method, apparatus, device and readable storage medium, to partially solve the above problems in the prior art.
The technical scheme adopted by the specification is as follows:
the present specification provides a data processing method including:
acquiring a routing table of a target frame; the routing table comprises the corresponding relation between each service request and a method for processing the calling of each type of service request by the controller layer;
identifying path rule information of each service request from the routing table;
judging whether the path rule information contains a target variable or not aiming at each path rule information;
if yes, updating the target variable in the path rule information into a wildcard regular expression;
traversing the path rule information of each service request, determining an updated routing table as a target routing table, wherein the target routing table is used for inquiring a method called by the controller layer for processing the service request sent by the user;
when a target service request is received, determining a method for processing the target service request and calling by the controller layer according to the target routing table and path information in a Uniform Resource Locator (URL) carried by the target service request, so as to execute a service corresponding to the target service request according to the determined method, wherein the path information of the URL is determined according to the routing table.
Optionally, a specified code is added to the target frame in advance through a probe, and the specified code is used for extracting a routing table of the target frame;
obtaining a routing table of a target frame specifically includes:
starting the target frame, and analyzing the mapping relation between the service requests of various types and the method for the controller layer to process the calling of the service requests of various types;
and responding to the execution of the method for configuring each analyzed mapping relation to the cache, running the specified code, extracting the type of each service request, the rule information of each path and the corresponding relation of the method called by the controller layer for processing each service request from each mapping relation, and constructing a routing table of the target frame.
Optionally, the determining whether the path rule information includes a target variable specifically includes:
judging whether the path rule information contains a designated symbol;
and if so, determining that the variable containing the designated symbol in the path rule information is a target variable.
Optionally, when a target service request is received, the method for the controller layer to process the target service request call is determined according to the target routing table and a uniform resource locator URL carried by the target service request, and specifically includes:
receiving target service requests sent by a plurality of users;
aiming at each target service request, acquiring a URL (uniform resource locator) carried by the target service request;
inquiring the target routing table according to the URL corresponding to the target service request, and determining a method for processing the target service request call by the controller layer;
and calling the target service requests with the same method in each target service request to serve as a group of target service requests, calling the corresponding method through the controller layer, and executing the service corresponding to each target service request in the group of target service requests.
Optionally, the method for the controller layer to process the target service request call is determined by querying the target routing table according to the URL corresponding to the target service request, and specifically includes:
segmenting the URL corresponding to the target service request, and extracting path information and a target service type corresponding to the target service request from the URL corresponding to the target service request;
searching a sub-target routing table corresponding to the target service type corresponding to the target service request from the target routing table according to the target service type corresponding to the target service request;
and matching the path information with the sub-target routing table, and determining a method for the controller layer to process the target service request call.
Optionally, matching the path information with the sub-target routing table to determine a method for the controller layer to process the target service request call, specifically including:
extracting the rule information of each path in the sub-target routing table;
judging whether the path information hits the extracted rule information of each path;
if so, according to the hit path rule information, searching the controller layer calling method corresponding to the hit path rule information in the sub-target routing table, and using the method as a method for the controller layer to process the target service request calling.
Optionally, the method further comprises:
when the abnormal service executed in the target frame is determined, acquiring the URL of the abnormal service;
extracting path information of the abnormal service from the URL of the abnormal service;
inquiring path rule information matched with the path information of the abnormal service in the target routing table;
and generating a control instruction according to the matched path rule information, and sending the control instruction to the controller layer to enable the controller layer not to execute the service corresponding to each URL of the matched path rule information.
The present specification provides a data processing apparatus comprising:
the acquisition module is used for acquiring a routing table of the target frame; the routing table comprises the corresponding relation between each service request and a method for the controller layer to process the calling of each type of service request;
the identification module is used for identifying the path rule information of each service request from the routing table;
the judging module is used for judging whether the path rule information contains a target variable or not aiming at each path rule information;
the updating module is used for updating the target variable in the path rule information into a wildcard regular expression if the target variable is the wildcard regular expression;
a first determining module, configured to traverse the path rule information of each service request, determine an updated routing table as a target routing table, where the target routing table is used to query a method called by the controller layer to process a service request sent by a user;
and the second determining module is used for normalizing path information in a Uniform Resource Locator (URL) carried by a target service request according to the target routing table when the target service request is received, determining a method for the controller layer to process the target service request according to a normalization result, and executing a service corresponding to the target service request according to the determined method, wherein the path information of the URL is determined according to the routing table.
The present specification provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements the above-described data processing method.
The present specification provides an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the above data processing method when executing the program.
The technical scheme adopted by the specification can achieve the following beneficial effects:
in the data processing method provided by this description, the target variable included in each path rule information in the routing table is updated to a wildcard regular expression in a manner of constructing a target routing table, and a correspondence between the path rule information corresponding to each service request including the wildcard regular expression and a method for the controller layer to process call of each service request is constructed. Therefore, the target variables in the route rule information of the routing table are updated to the wildcard regular expression, the route rule information matched with the URL route information carried by the received target service request in the target routing table can be accurately inquired, the method called by the controller layer for processing the target service request is further accurately obtained, and the efficiency of executing the service based on the URL is improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the specification and are incorporated in and constitute a part of this specification, illustrate embodiments of the specification and together with the description serve to explain the principles of the specification and not to limit the specification in a limiting sense. In the drawings:
FIG. 1 is a flow chart of a data processing method in the present specification;
FIG. 2 is a flow chart of a data processing method in the present specification;
FIG. 3 is a schematic diagram of a data processing apparatus provided herein;
fig. 4 is a schematic diagram of an electronic device corresponding to fig. 1 provided in the present specification.
Detailed Description
In order to make the objects, technical solutions and advantages of the present disclosure more clear, the technical solutions of the present disclosure will be clearly and completely described below with reference to the specific embodiments of the present disclosure and the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present disclosure, and not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present specification without any creative effort belong to the protection scope of the present specification.
In addition, it should be noted that all the actions of acquiring signals, information or data in the present invention are performed under the premise of complying with the corresponding data protection regulation policy of the country of the location and obtaining the authorization given by the owner of the corresponding device.
When the service is executed, the user can request to execute the relevant service by sending a service request carrying the URL. The URL may include a domain name, a service request type, a host name, path information, parameter information, and the like. The path information of the URL may be generated by an application configured by a terminal held by a user, based on path rule information agreed in advance with a service executing party executing the service, and a specific service type, and in some cases, a random number may be added to ensure security. Therefore, the URLs carried by the service requests may be different, but the methods called by the controller layer for processing the services corresponding to the URLs are the same, for example, the user a may request the same payment platform to execute the transfer services with different amounts at different times on the same day through the terminal, and at this time, the URLs sent by the user a requesting the same payment platform to execute the transfer services for multiple times may be classified into one category, so as to accurately find the method for processing the transfer service call, and improve the accuracy of service execution. Therefore, the URL normalization processing is carried out on different URLs which are called to be processed by the same method, the efficiency of searching and processing the method for calling the service corresponding to the URL can be improved, the accuracy of service response is improved, and the service execution efficiency is improved.
According to the scheme, a target routing table is constructed, a target variable in path rule information in the routing table is replaced by a wildcard regular expression, when a service request sent by a user is received, a Uniform Resource Locator (URL) carried by the service request can be matched with the target routing table, and as various types of service requests and a method for processing the corresponding call of the various types of service requests by a controller layer are recorded in the target routing table, the method for processing the received target service request call by the controller layer can be matched, so that a service corresponding to the target service request is executed.
The technical solutions provided by the embodiments of the present description are described in detail below with reference to the accompanying drawings.
Fig. 1 is a schematic flow chart of a data processing method provided in this specification.
S100: acquiring a routing table of a target frame; the routing table includes service requests and methods for the controller layer to process the service request calls.
Specifically, the execution subject of the method is an electronic device such as a server configured with a target framework, and the server can provide a service for executing the related service for the user based on the configured target framework. When a user requests to execute a service, a service request may be sent in the form of a URL, and the service request may also be sent with a corresponding URL, so that the method called by the controller layer to process the URL sent by the user needs to be found, so as to execute the service requested by the user.
When the Spring framework is started, the URLs of various types and the method for processing service request calls of various types by the controller layer are associated, and a mapping relation is established, so that a routing table of the target framework is constructed and put into a cache. The specific mode may be that when the Spring framework is started, an instance object (Bean) of a request mapping (@ RequestMapping) annotation is searched and analyzed, a definition rule of a URL path corresponding to each type of service request in the target framework is determined, and a correspondence between paths where methods called by the controller layer for executing each type of service request are located is determined, and the correspondence is placed in a cache after being determined. When the service is executed, the user can enable the service execution party to execute the service by sending the service request carrying the URL. And the service executing party determines a method called by the controller layer for processing the service corresponding to the URL according to the path rule of the URL, and then executes the service corresponding to the URL according to the determined method. However, in practical applications, the path information of the URL carried in the service request is determined according to the path rule information and the dynamic variable in the routing table, where the dynamic variable may be a random number or a random character string, and this specification is not limited thereto. That is, there is a difference between the path information of the URLs generated by using the same path rule information, and thus, there may be a case where services corresponding to different URLs can be handled by using the same method.
S102: identifying path rule information for each service request from the routing table.
Further, since the routing table records various types of service requests and the method for the controller layer to process various types of service request calls, in general, path information in the URL carried in the service request sent by the user is matched with path rule information recorded in the routing table one by one, so as to obtain a method for the controller layer to process the service request calls sent by the user. Although the scheme is accurate, the routing table records the path rule information of the URL in the Spring frame, the path rule information of the URL has a target variable, and the URL corresponding to each type of service request may be obtained by changing the target variable based on the path rule information of the URL. Therefore, the target variable in the path rule information in the routing table can be replaced by the wildcard regular expression to obtain the path rule information containing the wildcard regular expression, and as long as the path information in the URL carried by the service request sent by the user can hit the path rule information containing the wildcard regular expression, the method called by the controller layer for processing the service request can be queried. The path rule information may be a generation rule of path information of a URL configured in advance in the target frame, and the generation rule of the path information of the URL may be predetermined by the server configured with the target frame and the application client configured with the terminal device held by the user in this embodiment of the present specification. When the URL carried by the service request sent by the user is generated according to the generation rule of the path information of the URL, the server can match the URL corresponding to the service request with the target routing table of the target frame.
For example, assume table 1 is the routing table of the target framework:
it can be seen that "/api/{ id }/app/info" in the path rule information shown in table 1 may be a generation rule of URL path information, where "{ id }" is a target variable, the target variable may be changed according to a specific service requested to be executed by a user when generating a URL to generate the path information of the URL, and a method called by a controller layer to process a service request corresponding to such URL is "method", and a path of the controller method is "com.
In addition, in one or more embodiments of the present specification, the service request type includes existing services such as query service GET, add service POST, update service PUT, and DELETE service DELETE, and the present specification does not limit the specific service request type.
For example, the path information extracted from the URLs corresponding to the two service requests received by the target framework is "/api/123/application/info" and "/api/456/application/info", respectively, and the two URL paths can be obtained by matching and can be matched with "/api/{ id }/application/info", so that the method called by the controller layer to process the service requests corresponding to the two URLs is found to be "method da".
S104: and judging whether the path rule information contains a target variable or not aiming at each path rule information.
In general, the dynamic path in the path rule information may be replaced by a wildcard regular expression, the identification manner of the dynamic path may be to sequentially identify whether there is a designated symbol "{" according to the order from left to right of a plurality of symbols constituting the path rule information, and if there is a designated symbol "{", this indicates that the path rule information includes the dynamic path, and update the dynamic path to the wildcard regular expression, that is, may obtain the normalized path rule information corresponding to each service request, and the mapping relationship between the methods called by the controller to process each service request. As shown in table 2:
table 2 is a target routing table of the target framework, and it can be seen that the path rule information is "/api/{ id }/apply/info", and a target variable "{ id }" starting with a specified symbol "{" can be identified in the path rule information, and then "{ id }" can be replaced with a regular expression "([/s ] +)" to obtain a normalized path rule information of "/api/([/s ] +)/apply/info". Of course, the path rule information of a URL may include several target variables, such as the path rule information "/api/{ id }/apply/{ str }" in table 2, and two target variables "{ id }" and "{ str }" beginning with the designated symbol "{" may be identified in the path rule information, so that the updated path rule information may be,/api/([/s ] +)/apply/([/s ] +). Further, if there is no target rule information beginning with "{" in the path rule information, no update is necessary, and for example, if the path rule information in table 2 is "/api/user/application", the updated path rule information is not changed.
S106: and if so, updating the target variable in the path rule information into a wildcard regular expression.
If a target variable with a designated symbol "{" as the beginning is identified in the path rule information, updating variables in the "{ }" and the "{ }" into wildcard regular expressions, and obtaining updated path rule information containing the wildcard regular expressions.
If the target rule information beginning with the designation symbol "{" is not identified in the path rule information, the path rule information is not processed, that is, the path rule information not including the target variable and the updated path rule information are the same in the target routing table, and the normalized path rule information is still "/api/user/application" as shown in table 2.
S108: and traversing the path rule information of each service request, and determining an updated routing table as a target routing table, wherein the target routing table is used for inquiring a method called by the controller layer for processing the service request sent by the user.
And traversing the path rule information of each service request, identifying whether the path rule information of each service request contains a target variable or not aiming at the path rule information of each service request, updating the identified target variable into a generic regular expression, obtaining the updated path rule information corresponding to each service request, and further obtaining an updated routing table of a target frame, namely a target routing table. It is to be understood that, in the embodiment of the present specification, the number and the position of the target variable in the path rule information of the routing table are not limited.
S110: when a target service request is received, normalizing path information in a Uniform Resource Locator (URL) carried by the target service request according to the target routing table, determining a method for processing the target service request call by the controller layer according to a normalization result, and executing a service corresponding to the target service request according to the determined method, wherein the path information of the URL is determined according to the routing table.
In practical application, when the target frame receives the URL corresponding to the service request, the path information of the URL may be matched with the path rule information in the target routing table, so as to determine a method called by the controller layer to process the service request, and then execute the service requested by the service request according to the determined method.
Based on the data processing method shown in fig. 1, the target variable in each path rule information of the routing table is updated to a wildcard regular expression, so that the path rule information matched with the path information of the URL carried by the received target service request in the target routing table can be accurately inquired, the method called by the controller layer for processing the target service request can be accurately obtained, and the efficiency of executing the service based on the URL is improved.
In this embodiment of the present specification, acquiring the routing table in step S100 as shown in fig. 1 may be implemented by:
firstly, before a target frame is started, adding a specified code in the target frame through a probe in advance; the specified code is used to extract a routing table of the target frame.
In the Spring framework, a Java probe mode can be adopted to dynamically inject the designated code in advance, and the injected designated code is used for extracting the mapping relationship between each type of service request analyzed and the method for the controller layer to process each type of service request call when the Spring framework is started on the premise of not changing the original code of the Spring framework, so that the routing table of the target framework is constructed based on each mapping relationship, the original code of the Spring framework does not need to be modified, the routing table can be obtained, and the flexibility is ensured. It should be noted that the designated code is previously added to the target frame before the target frame is started, but it is not stated that the designated code is executed when the target frame is started. Since the designated code is used for the mapping relationship between the service requests of various types and the method for the controller layer to process the service request calls of various types, the execution machine of the designated code can analyze the mapping relationship between the service requests of various types and the method for the controller layer to process the service request calls of various types and store the analyzed mapping relationship into the cache.
Secondly, starting a target framework, and analyzing the mapping relation between the service requests of various types and the method for processing the service request call of various types by the controller layer.
In this step, when the Spring framework is started, the instance object Bean of the @ RequestMapping annotation is parsed, and a mapping relationship between each type of service request and a method for processing each type of service request call by the controller layer is determined. When a service request is obtained, the method for the controller layer to process the service request call can be determined through the URL carried by the service request and each mapping relation.
And then, responding to the execution of the method for configuring each analyzed mapping relation to the cache, running the specified code, extracting the type of each service request, the rule information of each path and the corresponding relation of the method called by the controller layer for processing each service request from each mapping relation, and constructing a routing table of the target frame.
The path rule information refers to a path generation rule of a URL preset in the target frame.
Generally, the timing for executing the designated code may be any timing after obtaining the mapping relationships between the service requests of the respective types and the methods called by the controller layer for processing the service requests of the respective types, and the routing table of the target frame may be constructed after the target frame is started. The specific time for constructing the routing table of the target framework may be determined according to a specific application scenario, which is not limited in this specification.
In this embodiment of the present specification, in the method for determining, according to the target routing table, that the controller layer processes the target service request to invoke when the target service request is received as shown in step S110 in fig. 1, path rule information matched with service requests sent by a plurality of users may also be determined according to the target routing table, and then a method for querying, by the controller layer, the controller layer to process each service request to invoke may be implemented in the following manner, as shown in fig. 2:
s200: target service requests sent by a plurality of users are received.
When a user sends a target service request to a server, the request can carry the URL corresponding to the target service request, a method required to be called for processing the target service request can be identified according to the URL, and the service corresponding to the target service request is processed by using the controller method. The URL corresponding to the target service request may include a domain name, a target service type, path information, and parameter information. The parameter information may include a user identifier, and the path information is generated according to the URL path rule information in the Spring framework and the type of the target service requested to be executed by the user in the actual application.
S202: and aiming at each target service request, acquiring a URL corresponding to the target service request.
Specifically, the target service request sent by the user may carry a URL corresponding to the target service request, and is used to instruct a controller layer in the target framework to process a method called by the target service request. The URL corresponding to the target service request may include a domain name, a target service type, path information, and parameter information. The parameter information may include a user identifier, and the path information is generated according to the URL path rule information in the Spring framework and the type of the target service requested to be executed by the user in the actual application.
S204: and segmenting the URL corresponding to the target service request, and extracting path information and the target service type corresponding to the target service request from the URL corresponding to the target service request.
Specifically, the domain name, the target service type, the path information, and the parameter information in the URL may be determined according to a preset URL generation rule, and may be separated by different symbols. The URL is segmented by the existing URL segmentation method to obtain the domain name target service type, the path information and the parameter information of the URL. And extracting the path information of the URL and the type of the target service, and determining a method for processing the target service request call by the controller layer based on the target routing table.
S206: and searching a sub-target routing table corresponding to the target service type from the target routing table according to the target service type.
Further, the target routing table may be segmented according to the target service type extracted from the URL corresponding to the target service request, so as to obtain a sub-target routing table corresponding to the target service type corresponding to the target service request. For example, the target routing table shown in table 2 includes two service request types, a query service GET and an add service POST. When the target service type corresponding to the target service request sent by the user is the query service GET, a part of the routing table corresponding to the query service type may be extracted, as shown in table 3, as a sub-routing table matched with the path information of the URL corresponding to the service request sent by the user. Table 3 is a sub-target routing table of the target frame, as follows:
s208: and extracting the route rule information in the sub-target routing table.
Specifically, a target routing table in a target frame may be obtained by the data processing method shown in fig. 1, where the target routing table is determined by updating a target variable in path rule information of the routing table to a wildcard regular expression, and therefore, path rule information including the wildcard regular expression exists in the target routing table.
S210: and judging whether the path information hits the extracted path rule information. If so, go to step S212, otherwise go to step S216.
Specifically, the rule information of each extracted path to judge whether the path information hits or not may adopt a longest regular matching rule. That is, the complete path information in the URL is matched with the extracted complete path rule information. For example, the path information of the URL is "/api/12345/app/info", and it can be seen that the path information of the URL may match with the path rule information "/api/{ id }/app/info" shown in table 3 above, but if the path information of the URL is "/api/12345/app", it may not match with the path rule information "/api/{ id }/app/info".
S212: and searching the method called by the controller layer corresponding to the hit path rule information in the sub-target routing table according to the hit path rule information, and using the method as a method for the controller layer to process the target service request call.
Generally, the target routing table includes the types of the service requests, the path rule information corresponding to the service requests, and the correspondence between the methods called by the controller layer for processing the service requests, and as long as the target service type corresponding to the target service request sent by the user and the path information of the URL corresponding to the target service request are determined, the method called by the controller layer for processing the target service request can be determined according to the correspondence.
S214: and calling the target service requests with the same method in each target service request to serve as a group of target service requests, calling the corresponding method through the controller layer, and executing the service corresponding to each target service request in the group of target service requests.
S216: and (6) ending.
As can be seen, in the method shown in fig. 2, based on the updated target routing table, the URL corresponding to the received target service request can be matched with the path rule information in the target routing table, so as to determine the method called by the controller layer to process the target service request, thereby improving the accuracy of service execution.
In an optional embodiment of this specification, after determining the target router in step S108 in fig. 1, the operation of stopping execution can be further performed according to the determined target router for the service of the abnormal condition occurring in the target frame, which can be determined as follows:
firstly, when determining that the service executed in the target frame is abnormal, acquiring the URL of the abnormal service.
In this step, if the executed service is abnormal, it is necessary to stop executing the abnormal service. The execution of the abnormal service is stopped, and the controller layer can not execute the abnormal service by issuing a control instruction according to the URL of the abnormal service. However, when a certain service is detected to be abnormal in the target frame, it may happen that other services belonging to the same service type as the detected abnormal service are also abnormal, but are not detected. At this time, according to the URL of the abnormal service and the target routing table determined when the target frame is started, other services belonging to the same category as the abnormal service may be determined, and the controller layer may stop executing the services, so as to prevent more abnormal situations from occurring.
And secondly, extracting the path information of the abnormal service from the URL of the abnormal service.
Specifically, the URL of the abnormal service is similar to the URL corresponding to the service request, and includes a domain name, a target service type, path information, and parameter information. The path information of the abnormal service is generated according to the path rule information in the Spring frame and the service type of the abnormal service.
Then, inquiring the path rule information matched with the path information of the abnormal service in the target routing table.
The path rule information corresponding to each service request is recorded in the target routing table, and the path rule information matched with the path information of the URL of the abnormal service can be searched in the target routing table according to the path information of the URL of the abnormal service. That is, by means of the scheme based on the path information of the URL of the abnormal service and the target routing table, the path rule of the URL of the abnormal service can be determined, the services corresponding to the URLs generated based on the path rule are all stopped from being executed, abnormal situations are checked one by one, and the problem of abnormal service execution caused by incomplete monitoring of the abnormal situations can be solved.
And finally, generating a control instruction according to the matched path rule information, and sending the control instruction to the controller layer to enable the controller layer not to execute the service corresponding to each URL of the matched path rule information.
Optionally, when determining that an abnormal condition occurs in a service executed in the target frame, the server may send the acquired URL of the abnormal service and the target routing table to the user, and the user determines, according to the path information in the URL of the abnormal service and the path rule information recorded in the target routing table, path rule information matched with the URL of the abnormal service, and sends, according to the path rule information obtained through matching, a control instruction to the controller layer, where the control instruction is used to enable the controller layer not to execute a service that hits each URL of the path rule information obtained through matching. Of course, monitoring the abnormal occurrence of the service executed in the target framework may also be performed by the user, which is not limited in this specification.
For example, the server finds a bug on a service corresponding to a URL shown in "http:// xxx.com/user/1234567/page. html", and since it is difficult to directly see whether there are other similar services from the URL corresponding to the abnormal service, it is only possible to issue the following control command to the controller layer to stop the execution of the abnormal service: "where host = ' xxx.com ' and url = '/user/1234567/page. This results in that when the execution of abnormal traffic is stopped, only the attack to the URL "/user/1234567/page.html" is restricted, and more of the corresponding traffic to the URLs of "/user/356678/page.html", "user/789151/page.html" and the like are not restricted, but these traffic are similar to the monitored abnormal traffic, and an abnormal situation is likely to occur, but they are still not monitored. If the path rule information in the target routing table is matched with the URL of the abnormal service, the path rule information matched with the "/user/1234567/page.html" is found to be "/user/([ ^ s ] +)/page.html", and based on the result, the user or the server can issue a control instruction: "where host = 'xxx.com' and url REGEXP '/user/([ ^ s ] +)/page.html'", thereby ensuring that other services belonging to the same category as the monitored abnormal service are successfully covered, and avoiding the problem that the execution of the service is stopped untimely due to the fact that the abnormal condition of other services is not monitored.
Based on the same idea, the data processing method provided in one or more embodiments of the present specification further provides a corresponding data processing apparatus, as shown in fig. 3.
Fig. 3 is a schematic diagram of a data processing apparatus provided in this specification, which specifically includes:
an obtaining module 300, configured to obtain a routing table of a target frame; the routing table comprises the corresponding relation between each service request and a method for the controller layer to process the calling of each type of service request;
an identifying module 302, configured to identify path rule information of each service request from the routing table;
a determining module 304, configured to determine, for each piece of path rule information, whether the piece of path rule information includes a target variable;
an updating module 306, configured to update the target variable in the path rule information to a wildcard regular expression if the target variable is the wildcard regular expression;
a first determining module 308, configured to traverse the path rule information of each service request, determine an updated routing table as a target routing table, where the target routing table is used to query a method called by the controller layer to process a service request sent by a user;
a second determining module 310, configured to, when a target service request is received, normalize, according to the target routing table, path information in a uniform resource locator URL carried by the target service request, and determine, according to a normalization result, a method for the controller layer to process the target service request call, so as to execute, according to the determined method, a service corresponding to the target service request, where the path information of the URL is determined according to the routing table.
Optionally, a specified code is added to the target frame in advance through a probe, and the specified code is used for extracting a routing table of the target frame;
optionally, the obtaining module 300 is specifically configured to start the target framework, and analyze a mapping relationship between each type of service request and a method called by the controller layer to process each type of service request; and responding to the execution of the method for configuring each analyzed mapping relation to the cache, running the specified code, extracting the type of each service request, the rule information of each path and the corresponding relation of the method called by the controller layer for processing each service request from each mapping relation, and constructing a routing table of the target frame.
Optionally, the determining module 304 is specifically configured to determine whether the path rule information includes a specified symbol; and if so, determining that the variable containing the designated symbol in the path rule information is a target variable.
Optionally, the second determining module 310 is specifically configured to receive target service requests sent by a plurality of users; aiming at each target service request, acquiring a URL (uniform resource locator) carried by the target service request; inquiring the target routing table according to the URL corresponding to the target service request, and determining a method for processing the target service request call by the controller layer; and calling the target service requests with the same method in each target service request to serve as a group of target service requests, calling the corresponding method through the controller layer, and executing the service corresponding to each target service request in the group of target service requests.
Optionally, the second determining module 310 is specifically configured to segment the URL corresponding to the target service request, and extract path information and a target service type corresponding to the target service request from the URL corresponding to the target service request; searching a sub-target routing table corresponding to the target service type corresponding to the target service request from the target routing table according to the target service type corresponding to the target service request; and matching the path information with the sub-target routing table, and determining a method for the controller layer to process the target service request call.
Optionally, the second determining module 310 is specifically configured to extract rule information of each path in the sub-target routing table; judging whether the path information hits the extracted rule information of each path; if so, according to the hit path rule information, searching the controller layer calling method corresponding to the hit path rule information in the sub-target routing table, and using the method as a method for the controller layer to process the target service request calling.
Optionally, the apparatus further comprises:
a control instruction generating module 312, configured to, when it is determined that the service executed in the target frame is abnormal, obtain a URL of the abnormal service; extracting path information of the abnormal service from the URL of the abnormal service; inquiring path rule information matched with the path information of the abnormal service in the target routing table; and generating a control instruction according to the matched path rule information, and sending the control instruction to the controller layer to enable the controller layer not to execute the service corresponding to each URL hitting the matched path rule information.
The present specification also provides a computer-readable storage medium storing a computer program, which can be used to execute the data processing method shown in fig. 1 described above.
This specification also provides a schematic block diagram of the electronic device shown in fig. 4. As shown in fig. 4, at the hardware level, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and may also include hardware required for other services. The processor reads a corresponding computer program from the non-volatile memory into the memory and then runs the computer program to implement the data processing method shown in fig. 1. Of course, besides the software implementation, the present specification does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may be hardware or logic devices.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present specification, and is not intended to limit the present specification. Various modifications and alterations to this description will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification should be included in the scope of the claims of the present specification.
Claims (10)
1. A method of data processing, the method comprising:
acquiring a routing table of a target frame; the routing table comprises the corresponding relation between each service request and a method for the controller layer to process the calling of each type of service request;
identifying path rule information of each service request from the routing table;
judging whether the path rule information contains a target variable or not according to each path rule information;
if yes, updating the target variable in the path rule information into a wildcard regular expression;
traversing the path rule information of each service request, determining an updated routing table as a target routing table, wherein the target routing table is used for inquiring a method called by the controller layer for processing the service request sent by the user;
when a target service request is received, normalizing path information in a Uniform Resource Locator (URL) carried by the target service request according to the target routing table, determining a method for processing the target service request call by the controller layer according to a normalization result, and executing a service corresponding to the target service request according to the determined method, wherein the path information of the URL is determined according to the routing table.
2. The method of claim 1, wherein the target frame is added with a specified code through a probe in advance, and the specified code is used for extracting a routing table of the target frame;
obtaining a routing table of a target frame specifically includes:
starting the target frame, and analyzing the mapping relation between the service requests of various types and the method for the controller layer to process the calling of the service requests of various types;
and responding to the execution of the method for configuring each analyzed mapping relation to the cache, running the specified code, extracting the type of each service request, the rule information of each path and the corresponding relation of the method called by the controller layer for processing each service request from each mapping relation, and constructing a routing table of the target frame.
3. The method of claim 1, wherein determining whether the path rule information includes a target variable specifically comprises:
judging whether the path rule information contains a designated symbol;
and if so, determining that the variable containing the designated symbol in the path rule information is a target variable.
4. The method according to claim 1, wherein when a target service request is received, determining, according to the target routing table and path information in a uniform resource locator URL carried by the target service request, a method for the controller layer to process the target service request call, specifically includes:
receiving target service requests sent by a plurality of users;
aiming at each target service request, acquiring a URL (uniform resource locator) carried by the target service request;
inquiring the target routing table according to the URL corresponding to the target service request, and determining a method for processing the target service request call by the controller layer;
and calling the target service requests with the same method in each target service request to serve as a group of target service requests, calling the corresponding method through the controller layer, and executing the service corresponding to each target service request in the group of target service requests.
5. The method according to claim 4, wherein the method for the controller layer to process the call of the target service request is determined by querying the target routing table according to the URL corresponding to the target service request, and specifically includes:
segmenting the URL corresponding to the target service request, and extracting the path information and the target service type corresponding to the target service request from the URL corresponding to the target service request;
searching a sub-target routing table corresponding to the target service type corresponding to the target service request from the target routing table according to the target service type corresponding to the target service request;
and matching the path information with the sub-target routing table, and determining a method for the controller layer to process the target service request call.
6. The method of claim 5, matching the path information with the sub-target routing tables, and determining the method for the controller layer to process the target service request call specifically comprises:
extracting the rule information of each path in the sub-target routing table;
judging whether the path information hits the extracted rule information of each path;
if so, according to the hit path rule information, searching the controller layer calling method corresponding to the hit path rule information in the sub-target routing table, and using the method as a method for the controller layer to process the target service request calling.
7. The method of claim 1, further comprising:
when the abnormal service executed in the target frame is determined, acquiring the URL of the abnormal service;
extracting path information of the abnormal service from the URL of the abnormal service;
inquiring path rule information matched with the path information of the abnormal service in the target routing table;
and generating a control instruction according to the matched path rule information, and sending the control instruction to the controller layer to enable the controller layer not to execute the service corresponding to each URL of the matched path rule information.
8. A data processing apparatus comprising:
the acquisition module is used for acquiring a routing table of the target frame; the routing table comprises the corresponding relation between each service request and a method for the controller layer to process the calling of each type of service request;
the identification module is used for identifying the path rule information of each service request from the routing table;
the judging module is used for judging whether the path rule information contains a target variable or not aiming at each path rule information;
the updating module is used for updating the target variable in the path rule information into a wildcard regular expression if the target variable is the wildcard regular expression;
a first determining module, configured to traverse the path rule information of each service request, determine an updated routing table as a target routing table, where the target routing table is used to query a method called by the controller layer to process a service request sent by a user;
and the second determining module is used for normalizing path information in a Uniform Resource Locator (URL) carried by a target service request according to the target routing table when the target service request is received, determining a method for the controller layer to process the target service request according to a normalization result, and executing a service corresponding to the target service request according to the determined method, wherein the path information of the URL is determined according to the routing table.
9. A computer-readable storage medium, storing a computer program which, when executed by a processor, implements the method of any of claims 1 to 7.
10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of any of claims 1 to 7 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210801014.8A CN114900546B (en) | 2022-07-08 | 2022-07-08 | Data processing method, device and equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210801014.8A CN114900546B (en) | 2022-07-08 | 2022-07-08 | Data processing method, device and equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114900546A CN114900546A (en) | 2022-08-12 |
| CN114900546B true CN114900546B (en) | 2022-09-16 |
Family
ID=82729807
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210801014.8A Active CN114900546B (en) | 2022-07-08 | 2022-07-08 | Data processing method, device and equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114900546B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115567444B (en) * | 2022-09-23 | 2024-02-27 | 北京香哈网络股份有限公司 | Controller routing address searching and calling method and system |
| CN117076991B (en) * | 2023-10-16 | 2024-01-02 | 云境商务智能研究院南京有限公司 | Power consumption abnormality monitoring method and device for pollution control equipment and computer equipment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108255870A (en) * | 2016-12-29 | 2018-07-06 | 中国移动通信集团浙江有限公司 | A kind of website data crawling method and device |
| CN110298005A (en) * | 2019-06-26 | 2019-10-01 | 上海观安信息技术股份有限公司 | The method that a kind of couple of URL is normalized |
| CN112163150A (en) * | 2020-09-17 | 2021-01-01 | 北京三快在线科技有限公司 | Information pushing method and device |
| CN112822302A (en) * | 2019-11-18 | 2021-05-18 | 百度在线网络技术（北京）有限公司 | Data normalization method and device, electronic equipment and storage medium |
| WO2022026272A1 (en) * | 2020-07-28 | 2022-02-03 | Palo Alto Networks, Inc. | Pattern-based malicious url detection |
| WO2022057002A1 (en) * | 2020-09-16 | 2022-03-24 | 厦门网宿有限公司 | Abnormal request processing method and device |
| CN114443990A (en) * | 2022-02-08 | 2022-05-06 | 北京百度网讯科技有限公司 | URL (Uniform resource locator) normalization method and device |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060265508A1 (en) * | 2005-05-02 | 2006-11-23 | Angel Franklin J | System for administering a multiplicity of namespaces containing state information and services |
| US20090164502A1 (en) * | 2007-12-24 | 2009-06-25 | Anirban Dasgupta | Systems and methods of universal resource locator normalization |
-
2022
- 2022-07-08 CN CN202210801014.8A patent/CN114900546B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108255870A (en) * | 2016-12-29 | 2018-07-06 | 中国移动通信集团浙江有限公司 | A kind of website data crawling method and device |
| CN110298005A (en) * | 2019-06-26 | 2019-10-01 | 上海观安信息技术股份有限公司 | The method that a kind of couple of URL is normalized |
| CN112822302A (en) * | 2019-11-18 | 2021-05-18 | 百度在线网络技术（北京）有限公司 | Data normalization method and device, electronic equipment and storage medium |
| WO2022026272A1 (en) * | 2020-07-28 | 2022-02-03 | Palo Alto Networks, Inc. | Pattern-based malicious url detection |
| WO2022057002A1 (en) * | 2020-09-16 | 2022-03-24 | 厦门网宿有限公司 | Abnormal request processing method and device |
| CN112163150A (en) * | 2020-09-17 | 2021-01-01 | 北京三快在线科技有限公司 | Information pushing method and device |
| CN114443990A (en) * | 2022-02-08 | 2022-05-06 | 北京百度网讯科技有限公司 | URL (Uniform resource locator) normalization method and device |
Non-Patent Citations (1)
| Title |
|---|
| 结合有监督广度优先搜索策略的通用垂直爬虫方法;高峰等;《计算机工程》;20181115(第11期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114900546A (en) | 2022-08-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106055574B (en) | Method and device for identifying illegal uniform resource identifier (URL) | |
| CN114900546B (en) | Data processing method, device and equipment and readable storage medium | |
| CN109768992B (en) | Webpage malicious scanning processing method and device, terminal device and readable storage medium | |
| WO2020248849A1 (en) | Webpage language switching method and apparatus, and terminal device | |
| CN109033403B (en) | Method, apparatus and storage medium for searching blockchain data | |
| CN111104664B (en) | Risk identification method of electronic equipment and server | |
| CN109743309B (en) | Illegal request identification method and device and electronic equipment | |
| CN109033406B (en) | Method, apparatus and storage medium for searching blockchain data | |
| CN108491715B (en) | Terminal fingerprint database generation method and device and server | |
| CN109101607B (en) | Method, apparatus and storage medium for searching blockchain data | |
| CN109450969B (en) | Method and device for acquiring data from third-party data source server and server | |
| CN110674427B (en) | Method, device, equipment and storage medium for responding to webpage access request | |
| CN111694992A (en) | Data processing method and device | |
| CN105354490A (en) | Method and device for processing hijacked browser | |
| CN111382179B (en) | Data processing method and device and electronic equipment | |
| CN110647463B (en) | Method and device for restoring test breakpoint and electronic equipment | |
| CN112286968A (en) | Service identification method, equipment, medium and electronic equipment | |
| CN111078435A (en) | Service processing method and device and electronic equipment | |
| CN111310137A (en) | Block chain associated data evidence storing method and device and electronic equipment | |
| CN111488371A (en) | Data query method and device | |
| CN105243134A (en) | Method and equipment for processing hijacked browser | |
| CN110717036A (en) | Method and device for removing duplication of uniform resource locator and electronic equipment | |
| CN113312540A (en) | Information processing method, device, equipment, system and readable storage medium | |
| CN111324778B (en) | Data and service processing method and device and electronic equipment | |
| CN109600418B (en) | Method, device, equipment and system for tracking application access |
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 |