Method, device and storage medium for debugging service request

Abstract

The application provides a service request debugging method and device, equipment and a storage medium. The method comprises the following steps: in response to any service request debugging operation, determining a service data source created for a service website where the service request is located; obtaining a dynamic login identifier of the service data source according to a website login state of the service data source under a configured session maintenance; and using the dynamic login identifier to realize the debugging of the service request. Through the session maintenance of the service data source, the long-term validity of the dynamic login identifier of the service data source is ensured, the dynamic login identifier is used to realize the debugging of the service request, and the short-term valid login identifier carried in the service request is no longer relied on, thereby avoiding the time limitation of the service request debugging, solving the problem of debugging failure caused by the expiration of the login identifier carried in the service request during the service request debugging, and greatly improving the success rate of the service request debugging.

Description

Technical Field

[0001] This application relates to the field of data transmission technology, specifically to a method, apparatus, device, and storage medium for debugging service requests. Background Technology

[0002] To analyze the network transmission performance of various business websites, network packet capture tools such as Fiddler, Charles, Firebug, Httpwatch, Wireshark, and mitmproxy are typically used to intercept various business requests involved in the network transmission process of the business websites. The data packets contained in the intercepted business requests are then retransmitted and edited to perform corresponding performance debugging for each business request.

[0003] Currently, when debugging each intercepted business request, the system relies on the login identifier (such as cookie information) carried in the request. However, since the login identifier in each business request has a certain validity period, each intercepted business request must be debugged within a very short validity period. Otherwise, if a business request has not been debugged before the login identifier expires, the debugging of that business request will fail. This results in a time limitation for debugging each business request, which greatly affects the success rate of debugging various business requests involved in the network transmission of the business website. Summary of the Invention

[0004] This application provides a method, apparatus, device, and storage medium for debugging business requests. By maintaining the session login status of the business data source created on the business website where any business request is located, the long-term validity of the dynamic login identifier of the business data source is ensured. This solves the problem of debugging failure caused by the expiration of the login identifier carried by the business request, avoids the time limitation of business request debugging, and greatly improves the success rate of business request debugging.

[0005] In a first aspect, embodiments of this application provide a method for debugging service requests, the method comprising:

[0006] In response to any business request, the debugging operation determines the business data source that has been created for the business website where the business request is located;

[0007] Based on the website login status of the business data source under the configured session persistence, obtain the dynamic login identifier of the business data source;

[0008] The dynamic login identifier is used to debug the business request.

[0009] Secondly, embodiments of this application provide a service request debugging apparatus, the apparatus comprising:

[0010] The data source determination module is used to determine the business data source that has been created for the business website where the business request is located in response to the debugging operation of any business request;

[0011] The dynamic identifier acquisition module is used to acquire the dynamic login identifier of the business data source based on the website login status of the business data source under the configured session persistence.

[0012] The request debugging module is used to debug the business request using the dynamic login identifier.

[0013] Thirdly, embodiments of this application provide an electronic device, which includes:

[0014] A processor and a memory, the memory being used to store a computer program, and the processor being used to invoke and run the computer program stored in the memory to execute the debugging method for the service request provided in the first aspect of this application.

[0015] Fourthly, embodiments of this application provide a computer-readable storage medium for storing a computer program that causes a computer to execute a debugging method for a business request as provided in the first aspect of this application.

[0016] Fifthly, embodiments of this application provide a computer program product, including a computer program / instruction, which, when executed by a processor, implements a debugging method for a business request as provided in the first aspect of this application.

[0017] This application provides a method, apparatus, device, and storage medium for debugging business requests. In response to a debugging operation of any business request, the method first determines the business data source that has been created for the business website where the business request is located, and checks the website login status of the business data source under configured session persistence to obtain the dynamic login identifier of the business data source. Through session persistence of the business data source, the long-term validity of the dynamic login identifier of the business data source can be ensured. Then, the business request is debugged using the dynamic login identifier, no longer relying on the short-term valid login identifier carried in the business request. This avoids the time limitation of business request debugging and solves the problem of debugging failure caused by the expiration of the login identifier carried in the business request, greatly improving the debugging success rate of business requests. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 A flowchart illustrating a debugging method for a service request, as shown in an embodiment of this application;

[0020] Figure 2 This is a flowchart illustrating a method for debugging and executing a service request, as shown in an embodiment of this application.

[0021] Figure 3 This is a screenshot of the request debugging page configured within the request debugging plugin as shown in an embodiment of this application.

[0022] Figure 4 This is a screenshot of the debug execution page configured within the request debug plugin, as shown in an embodiment of this application.

[0023] Figure 5 A flowchart illustrating another method for debugging a service request, as shown in an embodiment of this application;

[0024] Figure 6 This is a schematic block diagram of a service request debugging device shown in an embodiment of this application;

[0025] Figure 7 This is a schematic block diagram of an electronic device shown in an embodiment of this application. Detailed Implementation

[0026] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0027] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or server that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0028] To address the issue in existing technologies where debugging of a business request fails if the login identifier carried in the request expires before debugging is completed, thus limiting the time required for debugging, this application proposes a novel business request debugging method. This method pre-creates a corresponding business data source for any business website containing the business request, and then maintains the session login status of the created business data source on that website to ensure the long-term validity of the dynamic login identifier of the business data source. The dynamic login identifier of the business data source is then used to debug the business request, thereby avoiding the time limitations of business request debugging and resolving the problem of debugging failure due to the expiration of the login identifier carried in the business request.

[0029] Figure 1 This is a flowchart illustrating a debugging method for a service request, as shown in an embodiment of this application. (Refer to...) Figure 1 The method may include the following steps:

[0030] S110, in response to any business request debugging operation, determines the business data source that has been created for the business website where the business request is located.

[0031] Specifically, to address the issue of time limitations in business request debugging due to the short-term validity of login identifiers carried in business requests, this application embodiment requires that the login identifier selected for business request debugging be valid in the long term. Considering the potential delay between the initiation time and debugging time of the business request, the business website where the business request resides must maintain a corresponding login connection during the debugging operation. This ensures that a valid login identifier can be obtained during business request debugging without affecting the actual business processing of the business request within the business website.

[0032] Therefore, in this application embodiment, for each business website with business request debugging needs, a business data source associated with the business website will be created in advance. The business data source contains all data related to various businesses within the associated business website, so as to ensure that the login business of the associated business website can be simulated using the business data source without affecting the normal business processing within the actual business website.

[0033] It should be noted that when creating business data sources associated with various business websites, the main focus is on configuring the associated business data sources according to the security login requirements of each business website. Specifically, considering that commonly used login methods are mainly divided into four types: no login required, manual login, automatic login, and webpage simulation login, by analyzing the complexity of the security login requirements of each business website, one of these four login methods will be selected as the login method required for the associated business data sources of that business website. This ensures that the associated business data sources of each business website can be configured with one of the four login methods mentioned above.

[0034] For business data sources that select "no login required," no configuration is needed. For business data sources that select "automatic login," the login address (Uniform Resource Locator, URL) needs to be configured, along with the form parameters, login success characteristics, and CAPTCHA recognition parameters on the login page. This allows the backend to send login requests according to the configured login information and determine login success based on the returned results. If successful, the corresponding login identifier (such as cookie information) is saved to memory. For business data sources that select "manual login," only the login URL needs to be configured. Upon detecting a login trigger, the backend will redirect the user to the login page, requiring them to manually enter their username and password. The login identifier (cookie information) upon successful login is saved to memory. For business data sources that select "web page simulated login," since web page simulated login involves automatically clicking in the browser, corresponding login steps need to be configured. This allows the backend to utilize Selenium technology to automatically click, open, and close the browser, thus achieving login.

[0035] At this point, after creating the business data sources associated with each business website and configuring the corresponding login methods for each business data source, you can immediately log in to the business data source using the configured login method. Alternatively, you can log in to the business data source using the configured login method before debugging a specific business request within the business website associated with the business data source. This allows you to use the login identifier (i.e., cookie information) saved when successfully logging in to the business data source to debug the business request. This distinguishes the login identifier carried in the business request from the business request debugging, so that the business request debugging no longer depends on the short-term valid login identifier carried in the business request, thus avoiding the time limitations of business request debugging.

[0036] Optionally, when debugging any service request, the user first selects the service request to be debugged and performs the corresponding debugging operation. In this embodiment, in response to the debugging operation of any service request, the user first determines the service website where the service request to be debugged resides. Then, the user analyzes the identification information of the service data source associated with the service website to find the service data source already created for that service website. This allows the user to subsequently use the login identifier saved upon successful login to debug the service request, thus making the debugging of the service request independent of the short-lived login identifier carried in the service request.

[0037] S120: Obtain the dynamic login identifier of the business data source based on the website login status of the business data source under the configured session persistence.

[0038] As can be seen from the above analysis, the debugging of business requests in this application embodiment mainly relies on the login identifier of the business data source associated with the business website where the business request is located. In order to ensure the successful debugging of the business request at any time, the login identifier of the business data source is required to be valid for a long time.

[0039] Therefore, after creating the business data sources for each business website, corresponding session persistence is configured for each business data source. This session persistence enables the system to periodically send corresponding session requests to the business data source after logging in and obtain the session persistence response to determine whether the session persistence of the business data source is successful. This allows the business data source to remain logged in after successful login and to periodically and dynamically update the login identifier of the business data source (that is, the dynamic login identifier of the business data source in this embodiment). This ensures that the dynamic login identifier of the business data source is valid for a long time, thereby ensuring successful debugging of business requests at any time and avoiding the time limitations that exist when debugging business requests.

[0040] As an optional implementation, after debugging a business request and identifying the business data source already created on the business website for that request, the first step is to analyze the website login status of that business data source under configured session persistence. Considering that the dynamic login identifier of this business data source is needed during debugging, before executing the debugging operation, the user needs to actively log in to the business data source using the configured login method. The configured session persistence is then used to dynamically maintain the business data source in a continuously logged-in state, ensuring the dynamic login identifier of the business data source remains valid for a long time.

[0041] Therefore, after analyzing the website login status of the business data source under the configured session persistence, the dynamic login identifier saved when the business data source is logged in will be obtained directly based on the website login status.

[0042] S130 utilizes dynamic login identifiers to debug business requests.

[0043] Specifically, since the dynamic login identifier stored by the business data source under the configured session persistence is valid for a long time, this application embodiment can use the dynamic login identifier and, in combination with the URL, header parameters and request body of the business request, re-edit the corresponding business request, send it to the business data source, and obtain the corresponding response result returned by the business data source, thereby achieving successful debugging of the business request.

[0044] The technical solution provided in this application, in response to the debugging operation of any business request, first determines the business data source that has been created on the business website where the business request is located, and checks the website login status of the business data source under configured session persistence, thereby obtaining the dynamic login identifier of the business data source. Through session persistence of the business data source, the long-term validity of the dynamic login identifier of the business data source can be ensured. Then, the dynamic login identifier is used to implement the debugging of the business request, no longer relying on the short-term valid login identifier carried in the business request, thereby avoiding the time limitation of business request debugging, solving the problem of debugging failure caused by the expiration of the login identifier carried in the business request, and greatly improving the debugging success rate of business requests.

[0045] In addition, to ensure successful debugging of business requests, this application embodiment will pre-develop a new request debugging plugin for the above-mentioned technology, and execute the various debugging steps contained in the above-mentioned business request debugging method by calling the request debugging plugin.

[0046] In this embodiment, the request debugging plugin can be enabled in a browser to obtain each business request to be debugged and perform debugging operations on the business requests. The following provides a detailed explanation of how to use the request debugging plugin to obtain the debugging operations of the business requests before performing the above-mentioned actual debugging steps.

[0047] Figure 2 This is a flowchart illustrating the debugging and execution method of a service request as shown in an embodiment of this application, such as... Figure 2 As shown, the method may include the following steps:

[0048] S210, in response to the startup command of the request debugging plugin, pops up the corresponding request debugging page.

[0049] As an optional implementation, after a user enables a pre-developed request debugging plugin in their browser, a startup command for that plugin is generated. Then, in response to this startup command, the corresponding request debugging page pops up, such as... Figure 3 As shown, the request debugging page displays at least one business website, allowing the debugger to select the business website where the business request being debugged is located from among the various business websites.

[0050] S220, in response to the request interception instruction for the selected business website on the request debugging page, intercepts the business request that interacts with the business website and redirects to the debugging execution page.

[0051] After obtaining the business website selected by the debugging user, it is also necessary to obtain the business requests participating in this debugging within the selected business website. Therefore, after selecting a business website on the request debugging page, in response to the debugging user's request initiation command, various business requests will be sent to that business website. Simultaneously, the debugging user will perform corresponding request interception operations on the selected business website, thereby generating a request interception command for the selected business website. In response to this request interception command, during the process of sending various business requests to the selected business website, each business request interacting with that business website will be intercepted, so that the request debugging page will also display the intercepted business requests within the selected business website.

[0052] Furthermore, in order to trigger the debugging operation for any business request, the page will redirect from the request debugging page to the corresponding debugging execution page, such as... Figure 4As shown, the debugging execution page includes a debug selection box for business requests and a debug control. The debug selection box allows the debugging user to select a specific business request from the intercepted requests and automatically fill it into the selection box. The debug control allows the debugging user to enter a specific business request into the selection box and then execute the debugging operation for that request upon clicking it.

[0053] S230, in response to the trigger operation of the debug control, performs the corresponding debug operation on the business request entered in the debug selection box.

[0054] Optionally, the debugging user can detect the trigger operation of the debugging control by clicking the debugging control of the business request on the debugging execution page. Then, in response to the trigger operation, the business request entered in the debugging selection box will be obtained as the business request for this debugging, and the corresponding debugging operation will be performed on the business request. In response to the debugging operation of the business request, the various steps included in the above-mentioned business request debugging method will be executed.

[0055] Furthermore, considering that when performing actual debugging steps on a business request, it is first necessary to determine the business data source associated with the business website where the business request is located, before triggering the debugging control in the debugging execution page to start the actual debugging steps of the business request, the debugging user can manually associate the business data source of the business website where the business request is located in this debugging in the debugging execution page, so as to ensure the authenticity and accuracy of the business data source determined during subsequent business request debugging.

[0056] Among them, such as Figure 4 As shown, the debugging execution page can also include a control linking a business website to an existing business data source. This linking control, triggered by the debugging user's click, allows the user to manually select the business data source associated with the business website containing the current debugging request from among all existing business data sources. In other words, before executing the corresponding debugging operation on the business request entered in the debugging selection box, the associated business data source is set in response to the triggering operation of the linking control. By pre-linking the business website and business data source of the current debugging request, in response to the debugging operation of that request, the system can quickly and accurately determine the existing business data source for the business website containing the business request based on the identification information of the business data source recorded in the linking settings, ensuring the accuracy of the business data source determination.

[0057] Furthermore, to avoid the situation where the session persistence configured for the business data source fails and the business data source cannot remain in a logged-in state, this application embodiment will also provide a more detailed description of the steps for obtaining the dynamic login identifier of the business data source based on the website login status of the business data source under the configured session persistence.

[0058] Furthermore, considering that the dynamic login identifier of the business data source is needed when debugging business requests, before executing the corresponding debugging steps in response to the debugging operation of the business request, the debugging user needs to actively log in to the business data source through the configured login method, and the configured session persistence is used to dynamically maintain the business data source in a continuously logged-in state, so that the dynamic login identifier of the business data source is valid for a long time. Therefore, this application embodiment will also provide a more detailed description of the active login request situation of the business data source and the situation of dynamically updating the website login status of the business data source through session persistence.

[0059] Figure 5 This is a flowchart illustrating another method for debugging a service request, as shown in an embodiment of this application. Figure 5 As shown, the method may specifically include the following steps:

[0060] S510 responds to user login operations from the business data source and logs in to the business data source according to the login configuration of the business data source.

[0061] Since debugging a business request relies on the dynamic login identifier of the business data source associated with the business website where the business request is located, in order to ensure that the dynamic login identifier is valid for a long time, it is required that one be able to log in to the business data source associated with the business website where the business request is located before debugging the business request.

[0062] As an optional implementation, the login timing for the business data source can be either immediately after the business data source is created, or it can be at the moment before the business request is debugged. This embodiment does not limit this.

[0063] When logging into a newly created business data source, a user login operation for that business data source is detected. In response to this login operation, the system first retrieves the login configuration information pre-configured for that business data source. This configuration information may specify which of four login methods the business data source is configured for: no login required, automatic login, manual login, and web-based simulated login. Then, the system logs into the business data source using the actual login method configured for that business data source.

[0064] S520 calls the session persistence function configured for the business data source to periodically update the website login status of the business data source.

[0065] It should be understood that since business request debugging relies on the dynamic login identifier of the business data source, the dynamic login identifier of the business data source must be valid for a long time in order to achieve successful business request debugging. Therefore, after successfully logging into the business data source, this embodiment will also call the session persistence configured for the business data source, and periodically send a request to the logged-in business data source with the saved dynamic login identifier to keep the business data source in a logged-in state. When session persistence fails, the website login status of the business data source will be switched from logged-in to logged-out, thereby periodically updating the website login status of the business data source.

[0066] For example, the call to the session persistence configured for the business data source periodically updates the website login status of the business data source can be specifically: determining the call response result of the business data source to session persistence; and updating the website login status of the business data source according to the call response result and the session failure characteristic value configured under session persistence.

[0067] In other words, after calling the session persistence configured in the business data source, corresponding requests will be sent to the business data source periodically, and the response messages from each request will be obtained as the call response results for session persistence in this embodiment.

[0068] Furthermore, since it's necessary to determine the success of session persistence in real time when configuring it for business data sources, a corresponding session failure characteristic value is also configured during the session persistence configuration process. Then, after receiving the session persistence call response, the success of the session persistence can be determined by checking whether the response contains the configured session failure characteristic value, thereby dynamically updating the website login status of the business data source.

[0069] Specifically, considering that when session persistence is successful, the business data source will enter the corresponding website page, while when session persistence fails, the dynamic login identifier will become invalid. Therefore, the system will return to the login page of the business data source for re-login. Thus, the session failure characteristic value configured for session persistence can be a specific string that exists only on the login page of the business data source and does not appear on the various website pages of the business data source. For example, the session failure characteristic value could be the string represented by "Login Website".

[0070] S530, in response to any business request's debug operation, determines the business data source that has been created for the business website where the business request is located.

[0071] S540: Determine whether the business data source is logged in under the configured session persistence. If yes, execute S550; otherwise, execute S560.

[0072] When obtaining the dynamic login identifier of a business data source, it is first necessary to determine whether the business data source is already logged in under the configured session persistence to ensure that the dynamic login identifier is valid.

[0073] S550, parse the current login identifier of the business data source and use it as the dynamic login identifier.

[0074] If the business data source is logged in under the configured session persistence, then the currently saved login identifier of the business data source is directly parsed out. This login identifier is valid and serves as the dynamic login identifier of the business data source in this embodiment, so that the business request can be successfully debugged in the future using this dynamic login identifier.

[0075] S560 logs into the business data source according to the automatic login configuration of the business data source, and parses the login identifier after logging into the business data source as a dynamic login identifier.

[0076] If a business data source is in an unlogged-in state despite being configured for session persistence, there are two possibilities: 1) The debugging user did not actively log in to the business data source before debugging the business request; 2) The debugging user actively logged in to the business data source before debugging the business request, but the session persistence of the business data source failed.

[0077] Therefore, when the business data source is in an unlogged-in state under configured session persistence, it is first necessary to obtain the automatic login configuration of the business data source, and then automatically log back into the business data source according to the automatic login configuration, without requiring the debugging user to perform any login operation. Furthermore, after logging back into the business data source, the login identifier of the business data source is parsed. Since this login identifier is valid at this time, it is used as the dynamic login identifier of the business data source in this embodiment, so that the successful debugging of business requests can be achieved subsequently using this dynamic login identifier.

[0078] In addition, since the business data source may not have an automatic login method configured, and other login methods such as manual login are used instead, it is not possible to automatically log in to the business data source without the debugging user. Therefore, if the business data source is not logged in under the configured session persistence and the business data source is not configured to automatically log in, the website login identifier carried in the business request is used to debug the business request, or the debugging login prompt of the business data source is fed back and the debugging of the business request is exited.

[0079] In other words, if the business data source is not logged in and no automatic login is configured, it means that the business data source does not save a valid dynamic login identifier, making it impossible to use the dynamic login identifier of the business data source in this debugging. Therefore, the website login identifier carried in the business request in this debugging can be parsed to achieve the debugging of the business request.

[0080] However, due to a potential delay between the timing of debugging and the initiation of the service request, the website login identifier carried in the service request may expire, causing the debugging of this service request to fail. Therefore, to ensure successful debugging of the service request, this embodiment can also provide the debugging user with a debugging login prompt for the service data source. This prompt indicates that the service data source is not logged in and requires re-login. Furthermore, the debugging user can directly exit the current debugging of the service request. After the debugging user actively logs back into the service data source according to the debugging login prompt, the debugging of the service request can be executed again, thereby ensuring successful debugging of the service request.

[0081] S570 utilizes dynamic login identifiers to enable debugging of business requests.

[0082] In summary, the technical solution provided in this application, through session persistence configured in the business data source and debugging login prompts from users, enables successful login to the business data source in advance, ensuring that the business data source remains logged in at all times. This guarantees the long-term validity of the dynamic login identifier of the business data source, which is then used to debug business requests. This eliminates the reliance on short-term valid login identifiers carried in the business requests, thus avoiding the time limitations of business request debugging and solving the problem of debugging failure due to the expiration of login identifiers carried in business requests. This significantly improves the success rate of business request debugging.

[0083] Figure 6 This is a schematic block diagram illustrating a service request debugging device according to an embodiment of this application. Figure 6 As shown, the device 600 may include:

[0084] The data source determination module 610 is used to determine the business data source that has been created for the business website where the business request is located in response to the debugging operation of any business request.

[0085] The dynamic identifier acquisition module 620 is used to acquire the dynamic login identifier of the business data source based on the website login status of the business data source under the configured session persistence.

[0086] The request debugging module 630 is used to debug the business request using the dynamic login identifier.

[0087] Furthermore, the dynamic identifier acquisition module 620 can be specifically used for:

[0088] If the business data source is logged in under the configured session persistence, then the current login identifier of the business data source is parsed and used as the dynamic login identifier;

[0089] If the business data source is not logged in under the configured session persistence, then the business data source is logged in according to the automatic login configuration of the business data source, and the login identifier after logging in to the business data source is parsed as the dynamic login identifier.

[0090] Furthermore, the debugging device 600 for the service request may also include:

[0091] The debugging feedback module is used to debug the business request if the business data source is not logged in under the configured session persistence and the business data source is not configured to log in automatically, or to provide a debugging login prompt for the business data source and exit the current debugging of the business request.

[0092] Furthermore, the debugging device 600 for the service request may also include:

[0093] The data source login module is used to respond to the user login operation of the business data source and log in to the business data source according to the login configuration of the business data source.

[0094] The session persistence module is used to periodically update the website login status of the business data source by calling the session persistence configured for the business data source.

[0095] Furthermore, the session includes modules that can be specifically used for:

[0096] Determine the response result of the call to the session maintained by the business data source;

[0097] Based on the call response result and the session failure characteristic value configured under session persistence, the website login status of the business data source is updated accordingly.

[0098] Furthermore, the service request debugging device 600 is configured in a pre-developed request debugging plugin, and the device 600 may further include:

[0099] The plugin startup module is used to respond to the startup command of the plugin request and pop up the corresponding request debugging page, which displays at least one business website.

[0100] The request interception module is used to intercept business requests that interact with the selected business website in response to the request interception instruction on the request debugging page, and to jump to the debugging execution page, which is provided with a debugging selection box and debugging controls for the business request.

[0101] The debugging operation execution module is used to respond to the trigger operation of the debugging control and execute the corresponding debugging operation on the business request entered in the debugging selection box.

[0102] Furthermore, the debugging execution page also includes an association control between the business website and the created business data source;

[0103] Accordingly, the debugging device 600 for the service request may further include:

[0104] The data source association module is used to set the business data source associated with the business website in response to the trigger operation of the association control.

[0105] In this embodiment, in response to a debugging operation for any business request, the system first identifies the business data source already created on the business website where the business request resides, and checks the website login status of the business data source under configured session persistence. This allows the system to obtain the dynamic login identifier of the business data source. By maintaining the session of the business data source, the long-term validity of the dynamic login identifier can be ensured. Then, the system uses this dynamic login identifier to debug the business request, eliminating reliance on the short-term valid login identifier carried in the business request. This avoids the time limitations of business request debugging and solves the problem of debugging failure due to the expiration of the login identifier carried in the business request, greatly improving the success rate of business request debugging.

[0106] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be referred to the method embodiments. To avoid repetition, further details will not be provided here. Specifically, Figure 6 The apparatus 600 shown can execute any of the method embodiments in this application, and the foregoing and other operations and / or functions of each module in the apparatus 600 are respectively for implementing the corresponding processes in the various methods in the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0107] The apparatus 600 of this application embodiment has been described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that this functional module can be implemented in hardware, in software instructions, or in a combination of hardware and software modules. Specifically, the steps of the method embodiments in this application can be completed by integrated logic circuits in the processor's hardware and / or by software instructions. The steps of the method disclosed in this application embodiment can be directly embodied as being executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module can reside in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps in the above method embodiments.

[0108] Figure 7 This is a schematic block diagram of an electronic device 700 shown in an embodiment of this application.

[0109] like Figure 7 As shown, the electronic device 700 may include:

[0110] The system includes a memory 710 and a processor 720. The memory 710 stores computer programs and transfers the program code to the processor 720. In other words, the processor 720 can retrieve and run the computer program from the memory 710 to implement the methods described in the embodiments of this application.

[0111] For example, the processor 720 can be used to execute the above-described method embodiments according to instructions in the computer program.

[0112] In some embodiments of this application, the processor 720 may include, but is not limited to:

[0113] General-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0114] In some embodiments of this application, the memory 710 includes, but is not limited to:

[0115] Volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0116] In some embodiments of this application, the computer program may be divided into one or more modules, which are stored in the memory 710 and executed by the processor 720 to perform the method provided in this application. The one or more modules may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in the electronic device.

[0117] like Figure 7 As shown, the electronic device may further include:

[0118] Transceiver 730, which can be connected to processor 720 or memory 710.

[0119] The processor 720 can control the transceiver 730 to communicate with other devices; specifically, it can send information or data to other devices or receive information or data sent by other devices. The transceiver 730 may include a transmitter and a receiver. The transceiver 730 may further include antennas, and the number of antennas may be one or more.

[0120] It should be understood that the various components in the electronic device are connected through a bus system, which includes a data bus, a power bus, a control bus, and a status signal bus.

[0121] This application also provides a computer storage medium storing a computer program thereon, which, when executed by a computer, enables the computer to perform the methods of the above-described method embodiments. Alternatively, embodiments of this application also provide a computer program product containing instructions that, when executed by a computer, cause the computer to perform the methods of the above-described method embodiments.

[0122] When implemented using software, it can be implemented entirely or partially as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD)), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0123] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0124] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0125] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. For example, the functional modules in the various embodiments of this application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0126] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for debugging business requests, characterized in that, include: In response to any business request debugging operation, determine the business data source that has been created and associated with the business website where the business request is located. The business data source includes all data related to various businesses within the associated business website, which is used to simulate the login business implementation of the business website, and distinguish it from the normal business actually processed within the business website. Based on the website login status of the business data source under the configured session persistence, obtain the dynamic login identifier of the business data source; The dynamic login identifier is used to debug the business request; When applied to pre-developed request debugging plugins, the method further includes: In response to the startup command of the request debugging plugin, a corresponding request debugging page pops up, which displays at least one business website. In response to the request interception instruction of the selected business website in the request debugging page, the business request interacting with the business website is intercepted, and the user is redirected to the debugging execution page, which is equipped with a debugging selection box and debugging controls for the business request. In response to the triggering operation of the debugging control, the corresponding debugging operation is performed on the business request entered in the debugging selection box; Before performing the corresponding debugging operation on the business request entered in the debugging selection box, in response to the trigger operation of the associated control, the business data source associated with the business website is set.

2. The method according to claim 1, characterized in that, The step of obtaining the dynamic login identifier of the business data source based on the website login status of the business data source under configured session persistence includes: If the business data source is logged in under the configured session persistence, then the current login identifier of the business data source is parsed and used as the dynamic login identifier; If the business data source is not logged in under the configured session persistence, then the business data source is logged in according to the automatic login configuration of the business data source, and the login identifier after logging in to the business data source is parsed as the dynamic login identifier.

3. The method according to claim 2, characterized in that, The method further includes: If the business data source is not logged in under the configured session persistence and the business data source is not configured for automatic login, then the website login identifier carried in the business request is used to debug the business request, or the debugging login prompt of the business data source is fed back and the current debugging of the business request is exited.

4. The method according to claim 1, characterized in that, Before obtaining the dynamic login identifier of the business data source based on the website login status under configured session persistence, the method further includes: In response to a user login operation of the business data source, log in to the business data source according to the login configuration of the business data source; The session persistence mechanism configured for the business data source is invoked to periodically update the website login status of the business data source.

5. The method according to claim 4, characterized in that, The call to the session configured for the business data source periodically updates the website login status of the business data source includes: Determine the response result of the call to the session maintained by the business data source; Based on the call response result and the session failure characteristic value configured under session persistence, the website login status of the business data source is updated accordingly.

6. A debugging device for service requests, characterized in that, include: The data source determination module is used to respond to the debugging operation of any business request and determine the business data source that has been created and is associated with the business website for the business request. The business data source includes all data related to various businesses within the associated business website. It is used to simulate the login business implementation of the business website and distinguish it from the normal business actually processed within the business website. The dynamic identifier acquisition module is used to acquire the dynamic login identifier of the business data source based on the website login status of the business data source under the configured session persistence. A request debugging module is used to debug the business request using the dynamic login identifier; The debugging device is configured in a pre-developed request debugging plugin, and the device further includes: The plugin startup module is used to respond to the startup command of the plugin request and pop up the corresponding request debugging page, which displays at least one business website. The request interception module is used to intercept business requests that interact with the selected business website in response to the request interception instruction on the request debugging page, and to jump to the debugging execution page, which is provided with a debugging selection box and debugging controls for the business request. The debugging operation execution module is used to respond to the trigger operation of the debugging control and execute the corresponding debugging operation on the business request entered in the debugging selection box; The debugging execution page also includes a control linking the business website to the created business data source; The data source association module is used to set the business data source associated with the business website in response to the trigger operation of the associated control.

7. An electronic device, characterized in that, include: A processor and a memory, the memory being used to store a computer program, the processor being used to invoke and run the computer program stored in the memory to perform the debugging method for the service request according to any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, Used to store computer programs that cause a computer to execute a debugging method for a business request as described in any one of claims 1-5.

9. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instruction is executed by the processor, it implements the debugging method for the service request as described in any one of claims 1-5.

Images