CN116737598B

CN116737598B - Page debugging method, device, electronic equipment and computer readable medium

Info

Publication number: CN116737598B
Application number: CN202311015128.0A
Authority: CN
Inventors: 李子行; 曲昱晓; 刘振圻
Original assignee: State Grid Information and Telecommunication Co Ltd; Beijing Guodiantong Network Technology Co Ltd
Current assignee: State Grid Information and Telecommunication Co Ltd; Beijing Guodiantong Network Technology Co Ltd
Priority date: 2023-08-14
Filing date: 2023-08-14
Publication date: 2023-10-20
Anticipated expiration: 2043-08-14
Also published as: CN116737598A

Abstract

Embodiments of the present disclosure disclose a page debugging method, apparatus, electronic device, and computer-readable medium. One embodiment of the method comprises the following steps: receiving a service request information set, wherein each service request information comprises service interface address information and back-end terminal address information; each service request message is checked to obtain a target service request message set; for each target service request information: analyzing the service interface address information corresponding to the target service request information to obtain a service identifier; determining service instance information matched with the target service request information as peer service instance information to obtain a peer service instance information set; generating back-end service instance information based on the service identifier, the peer service instance information set and back-end terminal address information corresponding to the target service request information; and sending the target service request information to a back-end terminal for debugging the target page. The implementation mode can improve the efficiency of page debugging.

Description

Page debugging method, device, electronic equipment and computer readable medium

Technical Field

Embodiments of the present disclosure relate to the field of computer technology, and in particular, to a page debugging method, apparatus, electronic device, and computer readable medium.

Background

Page debugging is a technology for front-end personnel and back-end personnel to jointly debug related functions of pages. Currently, when page debugging is performed, the following methods are generally adopted: firstly, front-end personnel set a back-end service interface address for function joint debugging in a page to be debugged, and meanwhile, a back-end terminal starts various basic services and business services. Then, the front-end and the back-end jointly start page debugging.

However, the inventors found that when the above manner is adopted for page debugging, there are often the following technical problems:

firstly, when the same back-end terminal needs to be connected with a plurality of front-end terminals to debug a page, since the back-end needs to restart basic service each time the connection is switched, the page debugging is difficult to be performed in time, the time length of the front-end and back-end joint debugging is prolonged, and thus the page debugging efficiency is reduced;

secondly, the front end and the rear end generally need to perform multiple joint debugging on the same function in a short period, and if the front end and the rear end suspend joint debugging in the period, the front end needs to reset a joint debugging rear end terminal, so that the page debugging efficiency is reduced;

Thirdly, code faults are difficult to reproduce when page debugging is carried out in a test environment, or relevant logs are not clear enough when the code faults are reproduced, so that fault points are difficult to locate in time when page debugging is easy to cause, and page debugging efficiency is reduced;

fourth, when the front end and the back end are connected, original data is generally directly transmitted, so that the data is easy to leak in the transmission process, and the safety of the data is reduced.

The above information disclosed in this background section is only for enhancement of understanding of the background of the inventive concept and, therefore, may contain information that does not form the prior art that is already known to those of ordinary skill in the art in this country.

Disclosure of Invention

The disclosure is in part intended to introduce concepts in a simplified form that are further described below in the detailed description. The disclosure is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

Some embodiments of the present disclosure propose page debugging methods, apparatuses, electronic devices, and computer-readable media to solve one or more of the technical problems mentioned in the background section above.

In a first aspect, some embodiments of the present disclosure provide a page debugging method, the method comprising: receiving a service request information set aiming at a target page set, wherein the target page in the target page set is a page to be debugged, and each service request information in the service request information set comprises service interface address information and rear terminal address information, and the rear terminal address information characterizes a rear terminal; performing verification processing on each service request information in the service request information set to obtain a target service request information set; for each target service request information in the target service request information set, performing the steps of: responding to the fact that the back-end terminal address information corresponding to the target service request information meets the preset terminal condition, and analyzing the service interface address information corresponding to the target service request information to obtain a service identifier; determining service instance information in a preset service instance information set and matched with the target service request information in code version data as peer service instance information to obtain a peer service instance information set; generating back-end service instance information based on the service identifier, the peer service instance information set and back-end terminal address information corresponding to the target service request information; and sending the target service request information to a back-end terminal corresponding to the back-end service instance information so as to debug a target page corresponding to the target service request information.

In a second aspect, some embodiments of the present disclosure provide a page debugging apparatus, the apparatus comprising: a receiving unit configured to receive a service request information set for a target page set, where a target page in the target page set is a page to be debugged, and each service request information in the service request information set includes service interface address information and back-end terminal address information, where the back-end terminal address information characterizes a back-end terminal; the verification unit is configured to verify each service request information in the service request information set to obtain a target service request information set; an execution unit configured to execute, for each target service request information in the set of target service request information, the steps of: responding to the fact that the back-end terminal address information corresponding to the target service request information meets the preset terminal condition, and analyzing the service interface address information corresponding to the target service request information to obtain a service identifier; determining service instance information in a preset service instance information set and matched with the target service request information in code version data as peer service instance information to obtain a peer service instance information set; generating back-end service instance information based on the service identifier, the peer service instance information set and back-end terminal address information corresponding to the target service request information; and sending the target service request information to a back-end terminal corresponding to the back-end service instance information so as to debug a target page corresponding to the target service request information.

In a third aspect, some embodiments of the present disclosure provide an electronic device comprising: one or more processors; a storage device having one or more programs stored thereon, which when executed by one or more processors causes the one or more processors to implement the method described in any of the implementations of the first aspect above.

In a fourth aspect, some embodiments of the present disclosure provide a computer readable medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method described in any of the implementations of the first aspect.

The above embodiments of the present disclosure have the following advantageous effects: by the page debugging method of some embodiments of the present disclosure, the efficiency of page debugging can be improved. Specifically, the reason why the page debug efficiency is reduced is that: when the same back-end terminal needs to be connected with a plurality of front-end terminals to debug the page, since the back-end needs to restart basic service each time the connection is switched, the page debugging is difficult to be performed in time, the time length of the front-end and back-end joint debugging is increased, and thus the page debugging efficiency is reduced. Based on this, the page debugging method of some embodiments of the present disclosure first receives a service request information set for a target page set. The target pages in the target page set are pages to be debugged. Each service request information in the service request information set includes service interface address information and back-end terminal address information. The back-end terminal address information characterizes the back-end terminal. Therefore, each page debugging request of each front-end terminal can be obtained, and unified verification of each page debugging request can be conveniently carried out subsequently. And then, checking each service request information in the service request information set to obtain a target service request information set. Therefore, the service request meeting the debugging authority can be screened out through unified verification service, so that the service request can be directly distributed to each back-end terminal for execution. Finally, for each target service request information in the target service request information set, the following steps are performed: responding to the fact that the back-end terminal address information corresponding to the target service request information meets the preset terminal condition, and analyzing the service interface address information corresponding to the target service request information to obtain a service identifier; determining service instance information in a preset service instance information set and matched with the target service request information in code version data as peer service instance information to obtain a peer service instance information set; generating back-end service instance information based on the service identifier, the peer service instance information set and back-end terminal address information corresponding to the target service request information; and sending the target service request information to a back-end terminal corresponding to the back-end service instance information so as to debug a target page corresponding to the target service request information. Therefore, each service request meeting the debugging authority can be distributed to each corresponding back-end terminal according to the details of the service request. Therefore, according to the page debugging method of some embodiments of the present disclosure, unified authority check sum request distribution can be performed for front-end debugging requests from different pages, and each back-end terminal receiving the debugging requests does not need to start basic services (such as authority check), and only needs to wait for receiving the debugging requests, so that the back-end terminal can timely perform page debugging, and the duration of front-end and back-end joint debugging is shortened. Thus, page debug efficiency can be improved.

Drawings

The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale.

FIG. 1 is a flow chart of some embodiments of a page debugging method according to the present disclosure;

FIG. 2 is a schematic diagram of the structure of some embodiments of a page debugging device according to the present disclosure;

fig. 3 is a schematic structural diagram of an electronic device suitable for use in implementing some embodiments of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present disclosure.

It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings. Embodiments of the present disclosure and features of embodiments may be combined with each other without conflict.

It should be noted that the terms "first," "second," and the like in this disclosure are merely used to distinguish between different devices, modules, or units and are not used to define an order or interdependence of functions performed by the devices, modules, or units.

It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be understood as "one or more" unless the context clearly indicates otherwise.

The names of messages or information interacted between the various devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.

FIG. 1 illustrates a flow 100 of some embodiments of a page debugging method according to the present disclosure. The page debugging method comprises the following steps:

Step 101, a service request information set for a target page set is received.

In some embodiments, an execution body of the page debugging method may receive a set of service request information for a target set of pages. The target pages in the target page set may be pages to be debugged. The target pages in the target page set are associated with page version identifiers. The page version identification may uniquely identify the code version of the page-related function. The same destination page may be associated with multiple service request information. The service request information in the service request information set may be information sent by the front-end terminal, which requests the back-end terminal to execute the corresponding micro service. The front-end terminal may be a terminal for performing user interaction or data display with respect to the target page. The back-end terminal may be a terminal for storing and processing data. For example, the micro-services described above may include, but are not limited to, at least one of: user services, log services, file services, data queries, and data statistics. Each service request information in the service request information set may include service interface address information and back-end terminal address information. The backend terminal address information may characterize the backend terminal. The backend terminal address information may be an IP (Internet Protocol ) address corresponding to the backend terminal. The service interface address information may characterize a service interface address. The service interface address information may be a URL (Uniform Resource Locator ) string corresponding to the invoked micro service interface. The same backend terminal may be associated with multiple micro-service interfaces.

Alternatively, each service request information in the service request information set may be generated by the front-end terminal by:

the first step, obtaining the address information of the rear terminal from a preset browser local storage space. The local storage space of the browser can be a local storage space of the browser on the front-end terminal, wherein the local storage space is used for debugging pages. And selecting an attribute key value pair corresponding to the preset key name from each attribute key value pair stored in the local storage space of the browser according to the preset key name corresponding to the address information of the rear terminal, and determining the key value in the selected attribute key value pair as the address information of the rear terminal. The preset key name may be a preset key name. For example, the preset key name may be "toServer (target server terminal)".

In practice, the front-end debugger may set a key name "toServer" in the browser local storage space in advance, where the key value is an attribute key value pair of the back-end terminal IP address. Therefore, front-end debugging personnel can set the key value of the attribute key value pair taking the "toServer" as the key name according to the debugging requirement, and can dynamically acquire and modify the key value of the attribute key value pair in the front-end code without modifying more front-end codes due to the change of the debugging requirement.

And secondly, determining request header information and the address information of the rear-end terminal, which are included in preset initial service request information, as update request header information. The initial service request information may be request information that does not include an IP address corresponding to the backend terminal to be jointly debugged. The initial service request information may represent a request when the front-end terminal and the back-end terminal are debugged in a one-to-one joint manner. The request header information may include, but is not limited to, at least one of: network token value, HTTP (Hypertext Transfer Protocol ) request type, request source address information, service interface address. The network token value may be a string characterizing the identity of the user. The request source address information may characterize an address of a front-end terminal that initiates the service request. The request header information and the back-end terminal address information may be determined as update request header information by means of character concatenation.

And thirdly, based on the update request header information, updating the initial service request information to obtain the service request information. The execution body may update the request header information included in the initial service request information to the update request header information, and determine the updated initial service request information as service request information.

And 102, checking each service request message in the service request message set to obtain a target service request message set.

In some embodiments, the executing body may perform verification processing on each service request information in the service request information set to obtain a target service request information set. The target service request information in the target service request information set may be service request information with user login information. For each service request information in the service request information set, the following steps are performed:

and the first step is to respond to the network token value in the service request information, and to perform matching processing on the network token value in the service request information and the user login network token value in the preset user login network token value set, so as to obtain user matching information. The user login network token value in the user login network token value set may be a character string corresponding to the user logged in the micro service platform and representing the identity of the user. The user login network token values in the user login network token value set may correspond to the successfully logged-in users one by one. The user matching information may characterize whether the network token value in the service request information is the same as a user login network token value. First, in response to determining that the user login network token value set has the same user login network token value as the network token value in the service request information, a preset user abnormality-free identifier is determined as user matching information. The preset user no-abnormality identification can represent that the network token value in the service request information is the same as a user login network token value. Then, in response to determining that the user login network token value set does not exist, the user login network token value is the same as the network token value in the service request information, a preset user abnormality identification is determined as user matching information. The preset user anomaly identification may indicate that no arbitrary user login network token value is the same as the network token value in the service request information.

And a second step of determining the service request information as target service request information in response to determining that the user matching information satisfies a preset user matching condition. The preset user matching condition may be: the user matching information characterizes that the network token value in the service request information is the same as one user login network token value in the set of user login network token values.

Step 103, for each target service request information in the target service request information set, performing the following steps:

step 1031, in response to determining that the back-end terminal address information corresponding to the target service request information meets the preset terminal condition, performing parsing processing on the service interface address information corresponding to the target service request information to obtain the service identifier.

In some embodiments, the executing body may perform parsing processing on the service interface address information corresponding to the target service request information to obtain the service identifier in response to determining that the back-end terminal address information corresponding to the target service request information meets a preset terminal condition. The preset terminal condition may be that the back-end terminal represented by the back-end terminal address information corresponding to the target service request information and the front-end terminal sending the target service request information are different terminals. The service identifier may be a unique identifier for the micro-service. Firstly, the service interface address information corresponding to the target service request information is segmented through a character string segmentation algorithm, so that a path character string group is obtained. The path character string in the path character string group may be a sub-string of the character string corresponding to the service interface address information. And then, determining the path character string meeting the preset character string condition in the path character string group as a service identifier. The preset character string condition may be that the path character string is identical to at least one preset service identifier in the preset service identifier group. The preset service identifier in the preset service identifier group may be a unique identifier of the started micro service.

Optionally, before the analyzing the service interface address information corresponding to the target service request information to obtain the service identifier, the executing body may further execute the following steps:

and the first step, determining the sum of the request times count value corresponding to the preset counter and the preset value as an updated count value. The preset counter may be a preset counter for counting the target service request information. The request number count value may be the number of target service request information. The predetermined value may be 1.

And a second step of determining the updated count value as a request count value corresponding to the preset counter.

Step 1032, determining the service instance information in the preset service instance information set, in which the code version data is matched with the target service request information, as the same-level service instance information, and obtaining the same-level service instance information set.

In some embodiments, the executing body may determine, as peer service instance information, service instance information in which the code version data matches the target service request information in a preset service instance information set, and obtain a peer service instance information set. Wherein, the service instance information in the service instance information set corresponds to a target backend terminal in the target backend terminal set acquired in advance. The service instance information in the service instance information set may include, but is not limited to: service instance identification, instance address information, service name, running state value, and code version data. The service instance identifier may be a unique identifier for the micro-service instance. For example, the service instance identification may be a number. The above-described instance address information may characterize an IP address of a backend terminal providing a corresponding service. The service names may characterize the corresponding micro-services. The above-described operational status values may characterize the operational status of the micro-service. The above-described operating state may be, but is not limited to, one of the following: and (5) waiting for calling and calling. For example, the running state value may be 0, which characterizes the running state of the micro service as to be invoked. The code version data may include a version number and an update time. The update time may be a time of a code update corresponding to the version number. The target set of backend terminals may be a set of started backend terminals obtained from a registration module. The registration module may be a module for storing information of each micro service provided by the back-end terminal. The matching with the target service request information may be that the version number of the code version data corresponding to the service instance information is the same as the page version identifier of the target page corresponding to the target service request information.

Step 1033, generating back-end service instance information based on the service identifier, the peer service instance information set and the back-end terminal address information corresponding to the target service request information.

In some embodiments, the executing entity may generate the back-end service instance information based on the service identifier, the peer service instance information set, and back-end terminal address information corresponding to the target service request information in various manners. The backend service instance information may represent a backend terminal required for executing the micro service corresponding to the target service request information.

In some optional implementations of some embodiments, the executing entity may generate the back-end service instance information based on the service identifier, the peer service instance information set, and back-end terminal address information corresponding to the target service request information by:

and selecting the peer service instance information matched with the service identification from the peer service instance information set as target service instance information to obtain a target service instance information set. Wherein, the matching with the service identifier may be that the service name corresponding to the peer service instance information is the same as the service identifier.

And a second step of determining, as the back-end service instance information, the target service instance information in the set of target service instance information, which matches the back-end terminal address information corresponding to the target service request information, in response to determining that the target service instance information in the set of target service instance information exists. The target service instance information matched with the back-end terminal address information may be that instance address information corresponding to the target service instance information is the same as the back-end terminal address information.

Optionally, the executing body may further execute the following steps:

in the first step, in response to determining that the target service instance information matched with the back-end terminal address information corresponding to the target service request information does not exist in the target service instance information sequence, service instance calling information meeting preset matching conditions is selected from a preset service instance calling information set to serve as target service instance calling information, and a target service instance calling information set is obtained. The service instance calling information in the preset service instance calling information set can represent a calling record for calling the back-end terminal to execute the service request. The service instance invocation information in the service instance invocation information set may include, but is not limited to, at least one of: calling request address information, back-end terminal address information and expiration time. The call request address information may characterize an address of a front-end terminal that issues a service request. The expiration time may be a time when the corresponding service instance invocation information is no longer valid. The preset matching condition may be that call request address information corresponding to the service instance call information is the same as request source address information corresponding to the target service request information.

And a second step of determining the number corresponding to each target service instance information in the target service instance information set as an instance number value in response to determining that the target service instance calling information set satisfies a preset number condition. The preset number of conditions may be that the number of the target service instance call information in the target service instance call information set is smaller than a preset call record number. The preset call record number may be a preset lower limit value of the call number. For example, the preset call record number may be 1.

Alternatively, the target service instance information in the target service instance information set may include code version data, an operation state value, and a configuration data set. Wherein, the configuration data in the configuration data set may be detail data of the corresponding configuration item. The configuration items may include, but are not limited to, at least one of: memory, hard disk. The configuration data in the configuration data set may include a configuration item name, a total configuration amount, and a used amount. The total configuration amount may be the total amount of the corresponding configuration items. The used amount may be a used amount of the corresponding configuration item. The execution body may further execute the steps of:

Step one, in response to determining that the target service instance calling information set does not meet the preset number of conditions, a called service instance information set corresponding to the target service instance calling information set is determined. The called service instance information in the called service instance information set may characterize a called back-end terminal. For each target service instance call information in the target service instance call information set, the back-end terminal address information corresponding to the target service instance call information may be determined as called service instance information.

And step two, determining the intersection of the called service instance information set and the target service instance information set as a target back-end instance information set.

And step three, determining at least one preset version instance information in response to determining that the preset version instance information exists in the target back-end instance information set. The preset version instance information may be target back-end instance information in which the code version data satisfies a preset version condition. The preset version condition may be that the update time corresponding to the code version data is the latest time in the update times corresponding to the target back-end instance information set.

And step four, determining at least one preset state instance information in response to determining that the preset state instance information exists in the at least one preset version instance information. The preset state instance information may be preset version instance information in which the running state value satisfies a preset state condition. The preset state condition may be that an operation state value corresponding to the preset version instance information indicates that the micro service is ready.

And fifthly, in response to determining that the at least one preset state instance information meets the ready instance quantity condition, determining load information corresponding to each preset state instance information in the at least one preset state instance information based on each configuration data set corresponding to the at least one preset state instance information, and obtaining a load information group. The number of ready instances may be that the number of each preset state instance information in the at least one preset state instance information is greater than a preset terminal threshold. The preset terminal threshold may be a preset lower limit value of the number of terminals. For example, the preset terminal threshold may be 1. For each preset state instance information in the at least one preset state instance information, executing the following steps to obtain load information in the load information group:

A first sub-step of determining, for each configuration data in the configuration data set corresponding to the preset state instance information, a ratio of a used amount corresponding to the configuration data to a corresponding total configuration amount as a load value, and determining a product of the load value and a preset load weight value corresponding to the configuration data as a corrected load value. The preset load weight value may be a preset weight value corresponding to a configuration item.

And secondly, determining the sum of the correction load values corresponding to the preset state instance information as an instance load value.

And step three, determining the preset state instance information and the instance load value as load information.

And step six, determining preset state instance information corresponding to the load information meeting the preset minimum load condition in the load information group as back-end service instance information. The preset minimum load condition may be that an instance load value corresponding to the load information is a minimum value in each instance load value corresponding to the load information group.

The step of generating the back-end service instance information and the related content thereof are taken as an invention point of the embodiment of the disclosure, which solves the second technical problem mentioned in the background art that the front-end and the back-end generally need to perform multiple joint debugging on the same function in a short period, and if the front-end and the back-end suspend the joint debugging in the period, the front-end needs to reset the joint debugging back-end terminal, thereby reducing the page debugging efficiency. Factors that lead to reduced page debug efficiency tend to be as follows: the front-end and the back-end generally need to perform joint debugging on the same function for a plurality of times in a short period, and if the front-end and the back-end suspend joint debugging in the period, the front-end needs to reset the joint debugging back-end terminal. If the above factors are solved, the effect of improving the page debugging efficiency can be achieved. To achieve this, first, respective target service instance information associated with a debug request corresponding to a target page is determined according to a service identification. And then, the service instance calling information can be screened to obtain the previous instance calling record of the front-end terminal corresponding to the target page. Then, at least one back-end terminal which is co-tuned with the front-end terminal corresponding to the target page can be determined from the back-end terminals corresponding to the target service instance information. And finally, determining the back-end terminal with the minimum load after joint debugging as the back-end terminal for target page debugging. Therefore, the current back end needs to perform multiple joint debugging on the same function in a short period, and if the front end does not specify the back end address, the back end terminal can be determined directly according to the joint debugging record and the service interface address sent by the front end terminal. Therefore, the page debugging efficiency is improved.

And thirdly, generating back-end service instance information based on the request times count value corresponding to the preset counter, the target service instance information set and the instance number value. Wherein, first, according to the example number value, the above request count value is subjected to modulo processing, and the remainder after modulo processing is determined as an example identifier. Then, the target service instance information matched with the instance identification in the target service instance information set is determined as the back-end service instance information. Wherein, the matching with the instance identifier may be that the service instance identifier corresponding to the target service instance information is the same as the instance identifier.

Step 1034, the target service request information is sent to the back-end terminal corresponding to the back-end service instance information, so as to debug the target page corresponding to the target service request information.

In some embodiments, the execution body may send the target service request information to a backend terminal corresponding to the backend service instance information, so as to debug a target page corresponding to the target service request information. And after receiving the target service request information, the back-end terminal calls a corresponding service interface to debug a target page corresponding to the target service request information according to a service interface address corresponding to the target service request information.

Optionally, the executing body may further send the target service request information to a target front-end terminal for breakpoint debugging in response to determining that the address information of the back-end terminal corresponding to the target service request information does not meet the preset terminal condition. And the rear-end terminal corresponding to the target service request information and the front-end terminal sending the target service request information are the same terminal. The target front-end terminal may be a front-end terminal corresponding to the target service request information.

Optionally, before breakpoint debugging is performed, the target front-end terminal registers the micro-service corresponding to the target service request information into the test environment by executing a configuration file corresponding to the test environment.

The test environment configuration, the breakpoint debugging step and the related content are taken as an invention point of the embodiment of the disclosure, so that the technical problem mentioned in the background art is solved, namely the code fault is difficult to reproduce when the page debugging is performed in the test environment, or the related log is not clear enough when the code fault is reproduced, so that the fault point is difficult to position in time when the page debugging is easily caused, and the page debugging efficiency is reduced. Factors that lead to reduced page debug efficiency tend to be as follows: the code fault is difficult to reproduce when the page debugging is carried out in the test environment, or the relevant log is not clear enough when the code fault is reproduced, so that the page debugging is easy to cause that the fault point is difficult to locate in time. If the above factors are solved, the effect of improving the page debugging efficiency can be achieved. To achieve this effect, first, the target front-end terminal starts a local function service, and loads a configuration file corresponding to the test environment, thereby registering the local function service to the test environment. Then, the target front-end terminal sets the back-end terminal address corresponding to the page request as the target front-end terminal, so that the target front-end terminal can receive the page debugging request sent by the target front-end terminal. Finally, breakpoint debugging is started. Therefore, breakpoint debugging under the test environment can be realized by means of developing condition loading as the test environment, so that fault points can be positioned in time. Thus, page debug efficiency can be improved.

Optionally, the executing body may further execute the following steps:

the method comprises the steps of firstly, responding to received data query request information sent by a back-end terminal, and obtaining an electric power source data table from a preset electric power source database. The power source data table is stored in the power source database by a preset data input terminal. The preset data entry terminal may be a terminal providing a micro-service for data entry. The power source database may be a database storing electricity usage data. The power source data table may be a data table in which details of daily electricity consumption are recorded. The power source data table may include, but is not limited to: user number, date of electricity consumption, time series of electricity consumption. The above-described electricity consumption time series may be a series of electricity consumption at respective time points of the day corresponding to the date. The data query request information may be information requesting the micro service to perform a query data function.

And secondly, preprocessing the power source data table to obtain target power information. The target power information may represent an encrypted power source data table. The execution body may preprocess the power source data table in various ways to obtain the target power information.

In some alternative implementations of some embodiments, the power source data table may include a field identification sequence and a set of power source data records. The field identifier in the field identifier sequence may be a unique identifier of an attribute field corresponding to the power data. For example, the attribute field may be, but is not limited to, at least one of: date, time point, and amount of electricity. Each power source data record in the set of power source data records may include a sequence of field values. The field values in the sequence of field values may be attribute values of corresponding attribute fields. The executing body may preprocess the power source data set to obtain target power information by:

and step one, checking the field identification sequence included in the power source data table to obtain a key field information group. The key field information in the key field information set may be a field identifier corresponding to the sensitive data. For each field identifier in the field identifier sequence, determining the field identifier as key field information in response to determining that the target key identifier existing in the preset key identifier set is the same as the field identifier. The target key identifier may be the same preset key identifier as the field identifier.

And step two, for each power source data record in the power source data record group included in the power source data table, updating each field value matched with the key field information group in the field value sequence included in the power source data record to obtain an updated power source data record. Wherein, the matching with the key field information set may be that a field identifier corresponding to a field value in the field value sequence is the same as at least one field identifier corresponding to the key field information set. For each power source data record in the set of power source data records included in the power source data table, the following steps may be performed:

and a first sub-step of updating the field value in response to determining that the field identifier corresponding to the field value is identical to at least one field identifier corresponding to the key field information group for each field value in the field value sequence included in the power source data record. The updating process may be to replace the characters on each bit in the middle of the field value with preset characters. The preset character may be a preset character. For example, the predetermined character may be "×". It should be noted that, the execution body may dynamically replace the field value with a different character or replace a character on a different level according to the field type corresponding to the field value. For example, if the field value is "10437135" and the field type corresponding to the field value is "user number", the field value may be replaced with "user7135". If the field value is "1189" and the field type corresponding to the field value is "electricity consumption", the field value may be replaced with "1xx9".

And a sub-step II, in response to determining that the field value sequence is updated, determining the updated power source data record as an updated power source data record.

And thirdly, performing splicing processing on the obtained updated power source data record group to obtain spliced power source data. The spliced power source data may be a set of power data represented in a character string form. And connecting the updated power source data records in the updated power source data record group through a preset separator to obtain spliced power source data. The preset separator may be a preset character. For example, the separator may include, but is not limited to, at least one of: "$", "-and" # ".

And step four, generating an encryption key based on a preset character set. Wherein, the preset character set can be composed of numbers, capital letters and lowercase letters. Firstly, randomly selecting preset numerical values from the preset character set. Then, the selected preset characters are sorted according to the selection sequence. And finally, determining each sequenced preset character as an encryption key.

And fifthly, based on the encryption key, carrying out encryption processing on the spliced power source data to obtain encrypted power source data. The spliced power source data can be encrypted based on the encryption key through a first preset encryption algorithm, so that encrypted power source data can be obtained. The first preset encryption algorithm may be a preset symmetric encryption algorithm. For example, the first preset encryption algorithm may be a DES (Data Encryption Standard ) algorithm.

And step six, based on the pre-acquired public key, carrying out encryption processing on the encryption key to obtain key ciphertext data. The public key may be a key obtained from the backend terminal and generated by a second preset encryption algorithm. The public key is associated with a private key. The second preset encryption algorithm may be a preset asymmetric encryption algorithm. For example, the second predetermined encryption algorithm may be an RSA (Rivest-Shamir-Adleman) algorithm. The encryption key can be encrypted based on a pre-acquired public key through a second preset encryption algorithm, so that key ciphertext data can be obtained.

And seventhly, performing splicing processing on the encrypted power source data and the key ciphertext data to obtain target power information. And the encrypted power source data and the key ciphertext data can be spliced through a preset splicing character string to obtain target power information. The preset concatenation string may be a preset string for connecting encrypted data. For example, the preset concatenation string may be "_join_".

And thirdly, the target power information is sent to the back-end terminal so as to generate a data file corresponding to the service request information. The data file may be a file in which power consumption data has been written. The initial file may be a data file whose contents are empty.

Alternatively, the data file may be generated by:

the back-end terminal divides the target power information according to the preset splicing character string to obtain first encrypted data and second encrypted data. The first encrypted data may be encrypted power data. The second encrypted data may be an encrypted key.

And step two, the back-end terminal decrypts the second encrypted data according to the private key corresponding to the public key to obtain a key plaintext corresponding to the encryption key.

And thirdly, the back-end terminal decrypts the first encrypted data according to the key plaintext to obtain spliced power data plaintext corresponding to the spliced power source data.

And step four, the rear end terminal divides the spliced power data plaintext according to the separator to obtain a target power data set.

And fifthly, the back-end terminal writes the target power data in the target power data set into an initial file in a file stream mode so as to update the initial file.

And step six, the back-end terminal determines the updated initial file as a data file.

And step four, responding to the received data file sent by the back-end terminal, and sending the data file to the front-end terminal corresponding to the service request information for downloading.

And fifthly, determining front-end terminal address information corresponding to the front-end terminal, back-end terminal address information corresponding to the back-end terminal and pre-generated failure time as service instance calling information, and adding the service instance calling information to a preset service instance calling information set. The failure time may be pre-generated by the target response time and the effective duration. The target response time may be a time when the power integration data is transmitted to the front-end terminal. The effective duration may be a preset duration. The sum of the target response time and the effective duration may be determined as the expiration time.

The above-mentioned target power information generation step and its related content serve as an invention point of the embodiments of the present disclosure, solving the fourth technical problem mentioned in the background art, that "the security of data is reduced". Factors that lead to reduced security of data tend to be as follows: when the front end and the back end are connected, the original data is generally directly transmitted, so that the data is easy to leak in the transmission process. If the above factors are solved, the effect of improving the data security can be achieved. To achieve this effect, first, the power data corresponding to the query request is checked and identified, and the key field that needs desensitization processing is determined. And secondly, performing desensitization treatment on field values corresponding to the key fields to obtain an updated power source data record group. Then, the updated power source data record group is spliced to change the structure of the source data, so that the updated power source data record group is prevented from being directly identified when the data is leaked. And then, encrypting the spliced power source data through an encryption key so as to avoid direct identification when the data is leaked. The encryption key may then be encrypted for subsequent secure transmission of the encryption key to the backend terminal to decrypt the spliced power source data. And finally, performing splicing processing on the encrypted power source data and the key ciphertext data again to obtain the target power information. Therefore, the subsequent safe transmission of the power data to the back-end terminal is facilitated. Therefore, through the data desensitization and the mixed encryption mode, the risk of data leakage during front-end and back-end joint debugging can be reduced, and the safety of the data is improved.

With further reference to fig. 2, as an implementation of the method illustrated in the above figures, the present disclosure provides some embodiments of a page debugging device, which correspond to those method embodiments illustrated in fig. 1, and the device 200 is particularly applicable in various electronic apparatuses.

As shown in fig. 2, the page debugging device 200 of some embodiments includes: a receiving unit 201, a checking unit 202 and an executing unit 203. Wherein, the receiving unit 201 is configured to receive a service request information set for a target page set, where the target page in the target page set is a page to be debugged, and each service request information in the service request information set includes service interface address information and back-end terminal address information, and the back-end terminal address information characterizes a back-end terminal; a verification unit 202 configured to perform verification processing on each service request information in the service request information set to obtain a target service request information set; an execution unit 203 configured to execute, for each target service request information in the set of target service request information, the following steps: responding to the fact that the back-end terminal address information corresponding to the target service request information meets the preset terminal condition, and analyzing the service interface address information corresponding to the target service request information to obtain a service identifier; determining service instance information in a preset service instance information set and matched with the target service request information in code version data as peer service instance information to obtain a peer service instance information set; generating back-end service instance information based on the service identifier, the peer service instance information set and back-end terminal address information corresponding to the target service request information; and sending the target service request information to a back-end terminal corresponding to the back-end service instance information so as to debug a target page corresponding to the target service request information.

It will be appreciated that the elements described in the apparatus 200 correspond to the various steps in the method described with reference to fig. 1. Thus, the operations, features and resulting benefits described above for the method are equally applicable to the apparatus 200 and the units contained therein, and are not described in detail herein.

With further reference to fig. 3, a schematic structural diagram of an electronic device 300 suitable for use in implementing some embodiments of the present disclosure is shown. The electronic device shown in fig. 3 is merely an example and should not impose any limitations on the functionality and scope of use of embodiments of the present disclosure.

As shown in fig. 3, the electronic device 300 may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 301 that may perform various suitable actions and processes in accordance with a program stored in a Read Only Memory (ROM) 302 or a program loaded from a storage means 308 into a Random Access Memory (RAM) 303. In the RAM 303, various programs and data required for the operation of the electronic apparatus 300 are also stored. The processing device 301, the ROM 302, and the RAM 303 are connected to each other via a bus 304. An input/output (I/O) interface 305 is also connected to bus 304.

In general, the following devices may be connected to the I/O interface 305: input devices 306 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; an output device 307 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 308 including, for example, magnetic tape, hard disk, etc.; and communication means 309. The communication means 309 may allow the electronic device 300 to communicate with other devices wirelessly or by wire to exchange data. While fig. 3 shows an electronic device 300 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead. Each block shown in fig. 3 may represent one device or a plurality of devices as needed.

In particular, according to some embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, some embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such embodiments, the computer program may be downloaded and installed from a network via communications device 309, or from storage device 308, or from ROM 302. The above-described functions defined in the methods of some embodiments of the present disclosure are performed when the computer program is executed by the processing means 301.

It should be noted that, in some embodiments of the present disclosure, the computer readable medium may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In some embodiments of the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In some embodiments of the present disclosure, however, the computer-readable signal medium may comprise a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.

In some implementations, the clients, servers may communicate using any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol ), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the internet (e.g., the internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.

The computer readable medium may be embodied in the apparatus; or may exist alone without being incorporated into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a service request information set aiming at a target page set, wherein the target page in the target page set is a page to be debugged, and each service request information in the service request information set comprises service interface address information and rear terminal address information, and the rear terminal address information characterizes a rear terminal; performing verification processing on each service request information in the service request information set to obtain a target service request information set; for each target service request information in the target service request information set, performing the steps of: responding to the fact that the back-end terminal address information corresponding to the target service request information meets the preset terminal condition, and analyzing the service interface address information corresponding to the target service request information to obtain a service identifier; determining service instance information in a preset service instance information set and matched with the target service request information in code version data as peer service instance information to obtain a peer service instance information set; generating back-end service instance information based on the service identifier, the peer service instance information set and back-end terminal address information corresponding to the target service request information; and sending the target service request information to a back-end terminal corresponding to the back-end service instance information so as to debug a target page corresponding to the target service request information.

Computer program code for carrying out operations for some embodiments of the present disclosure may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

The flowcharts 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 disclosure. 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 some embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware. The described units may also be provided in a processor, for example, described as: a processor includes a receiving unit, a checking unit, and an executing unit. Where the names of the units do not constitute a limitation of the unit itself in some cases, for example, the receiving unit may also be described as "a unit that receives a service request information set for a target page set".

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by those skilled in the art that the scope of the invention in the embodiments of the present disclosure is not limited to the specific combination of the above technical features, but encompasses other technical features formed by any combination of the above technical features or their equivalents without departing from the spirit of the invention. Such as the above-described features, are mutually substituted with (but not limited to) the features having similar functions disclosed in the embodiments of the present disclosure.

Claims

1. A method of page debugging, comprising:

receiving a service request information set aiming at a target page set, wherein the target page in the target page set is a page to be debugged, and each service request information in the service request information set comprises service interface address information and rear terminal address information, and the rear terminal address information characterizes a rear terminal;

performing verification processing on each service request information in the service request information set to obtain a target service request information set;

for each target service request information in the set of target service request information, performing the steps of:

responding to the fact that the back-end terminal address information corresponding to the target service request information meets the preset terminal condition, and analyzing the service interface address information corresponding to the target service request information to obtain a service identifier;

determining service instance information in a preset service instance information set and matched with the target service request information by code version data as peer service instance information to obtain a peer service instance information set;

generating back-end service instance information based on the service identifier, the peer service instance information set and back-end terminal address information corresponding to the target service request information;

And sending the target service request information to a back-end terminal corresponding to the back-end service instance information so as to debug a target page corresponding to the target service request information.

2. The method of claim 1, wherein each service request information in the set of service request information is generated by a front-end terminal by:

acquiring address information of a rear terminal from a preset browser local storage space;

determining request header information and the address information of the rear terminal included in preset initial service request information as update request header information;

and based on the update request header information, performing update processing on the initial service request information to obtain service request information.

3. The method of claim 1, wherein before the parsing process is performed on the service interface address information corresponding to the target service request information to obtain a service identifier, the method further includes:

determining the sum of the request count value corresponding to the preset counter and the preset value as an updated count value;

and determining the updated count value as a request number count value corresponding to the preset counter.

4. A method as recited in claim 3, wherein the generating back-end service instance information based on the service identification, the peer service instance information set, and back-end terminal address information corresponding to the target service request information comprises:

Selecting peer service instance information matched with the service identification from the peer service instance information set as target service instance information to obtain a target service instance information set;

and in response to determining that the target service instance information set has target service instance information matched with the back-end terminal address information corresponding to the target service request information, determining the target service instance information matched with the back-end terminal address information in the target service instance information set as back-end service instance information.

5. The method of claim 4, wherein the method further comprises:

in response to determining that the target service instance information set does not have target service instance information matched with the back-end terminal address information corresponding to the target service request information, selecting service instance calling information meeting preset matching conditions from a preset service instance calling information set as target service instance calling information, and obtaining a target service instance calling information set;

in response to determining that the set of target service instance call information meets a preset number condition, determining the number corresponding to each piece of target service instance information in the set of target service instance information as an instance number value;

And generating back-end service instance information based on the request times count value corresponding to the preset counter, the target service instance information set and the instance number value.

6. The method according to one of claims 1-5, wherein the method further comprises:

and in response to determining that the address information of the rear-end terminal corresponding to the target service request information does not meet the preset terminal condition, sending the target service request information to a target front-end terminal for breakpoint debugging.

7. The method of claim 6, wherein the method further comprises:

responding to the received data query request information sent by the back-end terminal, and acquiring an electric power source data table from a preset electric power source database, wherein the electric power source data table is stored in the electric power source database by a preset data entry terminal;

preprocessing the power source data table to obtain target power information;

the target power information is sent to the back-end terminal so as to generate a data file corresponding to the service request information;

transmitting the data file to a front-end terminal corresponding to the service request information for downloading in response to receiving the data file transmitted by the back-end terminal;

And determining front-end terminal address information corresponding to the front-end terminal, back-end terminal address information corresponding to the back-end terminal and pre-generated failure time as service instance calling information, and adding the service instance calling information to a preset service instance calling information set.

8. A page debugging device, comprising:

a receiving unit configured to receive a set of service request information for a set of target pages, wherein the target pages in the set of target pages are pages to be debugged, each service request information in the set of service request information includes service interface address information and back-end terminal address information, and the back-end terminal address information characterizes a back-end terminal;

the verification unit is configured to verify each service request information in the service request information set to obtain a target service request information set;

an execution unit configured to, for each target service request information in the set of target service request information, execute the steps of:

9. An electronic device, comprising:

one or more processors;

a storage device having one or more programs stored thereon,

when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-7.

10. A computer readable medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the method of any of claims 1-7.