Server access method, routing rule configuration method, service code generation method, equipment, storage medium and program product

Abstract

The embodiment of the invention provides a server access method, a routing rule configuration method, a service code generation method, equipment, a storage medium and a program product. In the embodiment of the invention, terminal equipment scans a service code to obtain link information, and the link information comprises server identification information bound with the service code and a configuration indicator; the terminal equipment sends a routing configuration request, and the routing configuration request is forwarded to the configuration node through the reverse proxy node under the indication of the configuration indicator; and the configuration node configures a corresponding routing rule for the reverse proxy node according to the identification code of the terminal device and the identification information of the server bound with the service code, so that the reverse proxy node routes a service access request from the terminal device to the server bound with the service code based on the configured routing rule. Therefore, the routing rule is configured for the access of the code-scanned link information, the tedious operation of frequent manual configuration of testers is reduced, the operation is simple, the configuration efficiency is improved, and the test efficiency is further improved.

Description

Technical Field

[0001] The present application relates to the field of the Internet, and in particular to a server access method, a routing rule configuration method, a service code generation method, a device, a storage medium, and a program product. Background Art

[0002] When deploying test versions, developers can deploy test versions of different applications on different physical clusters. In the same physical cluster, different test versions of the same application can be deployed on different servers to achieve physical isolation and avoid mutual interference between different test versions.

[0003] In order to uniformly access and manage multiple servers, a reverse proxy node is added before these servers. The reverse proxy node is responsible for intercepting access requests from clients and then sending the access requests to the corresponding server.

[0004] When testing different versions of an application, testers need to use a third-party tool to open the reverse proxy node's configuration page. There, they need to configure routing rules pointing to the server where the version under test resides, so that the reverse proxy node can forward test requests to the corresponding server. If testing between different versions is required, testers must frequently manually configure routing rules, which is cumbersome and inefficient, hindering testing efficiency. Summary of the Invention

[0005] Multiple aspects of the present application provide a server access method, a routing rule configuration method, a service code generation method, a device, a storage medium, and a program product to reduce the tedious operation of frequently manually configuring routing rules, improve configuration efficiency, and thereby improve testing efficiency.

[0006] An embodiment of the present application provides a server access method, which is applied to a terminal device, the method comprising: in response to a scanning operation of the terminal device on a target service code, parsing target link information from the target service code, the target link information including an access address of a reverse proxy node, a configuration node indicator, and identification information of at least one target server bound to the target service code, the configuration node indicator being used to point to a configuration node, and the configuration node being used to configure at least one target routing rule corresponding to the at least one target server for the reverse proxy node; generating a routing configuration request based on the target link information, the routing configuration request including at least the configuration node indicator and the at least one target server; The invention relates to a method for transmitting a routing configuration request to the reverse proxy node according to the access address, so that the reverse proxy node can configure the at least one target routing rule through the configuration node according to the configuration node indicator, wherein each target routing rule includes the identification information of a target server and the identification code of the terminal device, and the identification code is the unique identity identifier of the terminal device in the target routing rule; the invention relates to a method for transmitting a routing configuration request to the reverse proxy node according to the access address, so that the reverse proxy node can forward the routing configuration request to the at least one target server according to the identification code based on the at least one target routing rule, and the service access request includes the identification code.

[0007] An embodiment of the present application also provides a routing rule configuration method, which is applied to a configuration node, the method comprising: receiving a routing configuration request sent by a reverse proxy node, the routing configuration request comprising at least: a configuration node indicator and identification information of at least one target server bound to a target service code, the routing configuration request being generated by a terminal device based on target link information contained in the target service code, the target link information comprising an access address of the reverse proxy node, the configuration node indicator, and identification information of the at least one target server; the configuration node indicator being used to point to the configuration node; determining an identification code of the terminal device; configuring at least one target routing rule for the reverse proxy node based on the identification code and the identification information of the at least one target server, so that the reverse proxy node forwards a server access request from the terminal device to the at least one target server based on the at least one target routing rule; each target routing rule comprising identification information of a target server and the identification code.

[0008] An embodiment of the present application also provides a server access method, which is applied to a reverse proxy node, the method comprising: receiving a routing configuration request sent by a terminal device, the routing configuration request including a configuration node indicator and identification information of at least one target server bound to a target service code; the routing configuration request is generated by the terminal device based on target link information contained in the target service code, the target link information including the access address of the reverse proxy node, the configuration node indicator and identification information of the at least one target server, the configuration node indicator is used to point to a configuration node, and the configuration node is used to configure at least one target routing rule corresponding to the at least one target server for the reverse proxy node; forwarding the routing configuration request to the configuration node for the configuration node to configure the at least one target routing rule; each target routing rule includes identification information of a target server and an identification code of the terminal device; receiving a server access request sent by the terminal device, the service access request including the identification code; if the at least one target routing rule is determined based on the identification code, forwarding the server access request to the at least one target server based on the at least one target routing rule.

[0009] An embodiment of the present application also provides a service code generation method, which is applied to a first terminal device, the method comprising: displaying a target page, the target page displaying identification information of multiple servers; determining at least one target server in response to a selection operation on the multiple servers; generating a target service code based on the identification information of the at least one target server, the access address of the reverse proxy node and the configuration node indicator, the target service code comprising target link information, the target link information comprising the access address of the reverse proxy node, the configuration node indicator and the identification information of the at least one target server; the configuration node indicator is used to point to a configuration node, the configuration node is used to configure at least one target routing rule corresponding to the at least one target server for the reverse proxy node; and providing the target service code to a second terminal device so that the second terminal device can access the at least one target server based on a scanning operation of the target service code.

[0010] An embodiment of the present application also provides an electronic device, including a memory and a processor, wherein the memory is used to store a computer program, and the processor is coupled to the memory and is used to execute the computer program to implement the steps in the various methods provided in the embodiments of the present application.

[0011] An embodiment of the present application further provides a computer-readable storage medium storing a computer program, which, when executed by a processor, enables the processor to implement the steps in the above-described method.

[0012] An embodiment of the present application further provides a computer program product, which includes a computer program / instructions. When the computer program / instructions are executed by a processor, the processor is enabled to implement the steps in the above method embodiment.

[0013] In an embodiment of the present application, a terminal device scans a service code to obtain link information, which includes server identification information and a configuration indicator bound to the service code; the terminal device sends a routing configuration request, which is forwarded to the configuration node via the reverse proxy node under the instruction of the configuration indicator; the configuration node configures corresponding routing rules for the reverse proxy node based on the identification code of the terminal device and the identification information of the server bound to the service code, so that the reverse proxy node can route the service access request from the terminal device to the server bound to the service code based on the configured routing rules, thereby configuring routing rules for access to the link information scanned out, reducing the tedious operations that testers need to frequently manually configure, simplifying the operation, improving configuration efficiency, and thereby improving testing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0015] Figure 1 An interactive diagram of a service access method provided by an exemplary embodiment of the present application;

[0016] Figure 2 A flowchart of a method for generating a service code provided by another exemplary embodiment of the present application;

[0017] Figure 3 A schematic diagram of the structure of a target page provided for another exemplary embodiment of the present application;

[0018] Figure 4 A flowchart of another service access method provided as another exemplary embodiment of the present application;

[0019] Figure 5 A flowchart of another routing rule configuration method provided by another exemplary embodiment of the present application;

[0020] Figure 6 A flowchart of another server access method provided as another exemplary embodiment of the present application;

[0021] Figure 7 A schematic structural diagram of an electronic device provided as another exemplary embodiment of the present application;

[0022] Figure 8A schematic structural diagram of a server access device provided by an exemplary embodiment of the present application;

[0023] Figure 9 A schematic structural diagram of a routing rule configuration device provided by an exemplary embodiment of the present application;

[0024] Figure 10 A schematic structural diagram of a server access device provided by an exemplary embodiment of the present application;

[0025] Figure 11 A schematic structural diagram of a service code generating device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0026] To make the purpose, technical solutions, and advantages of this application more clear, the technical solutions of this application will be clearly and completely described below in conjunction with the specific embodiments of this application and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0027] It should be noted that, in the case of user information involved in the embodiments of the present application, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in the embodiments of the present application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse. In addition, the various models involved in this application (including but not limited to language models or large models) are in compliance with relevant laws and standards.

[0028] In addition, it should be noted that when the embodiments of the present application involve user interaction operations or triggering operations, the user interaction operations or triggering operations involved in the embodiments of the present application include but are not limited to: touch operations, gesture operations, voice operations, head movement operations, eye movement operations and other interactive operations in various ways; among which, touch operations include but are not limited to: click operations, double-click operations, long press operations, sliding operations, pinch operations or mouse hover operations, etc. Sliding operations include but are not limited to: straight sliding, curved sliding, etc.

[0029] Furthermore, it should be noted that, in the case where the embodiment of the present application involves jumping between the first interface and the second interface, the jumping method involved in the embodiment of the present application includes but is not limited to: jumping directly from the first interface to the second interface, jumping from the first interface to the task interface first and jumping to the second interface after completing the corresponding task operation on the task interface; completing the corresponding task operation on the task interface includes but is not limited to: when the task interface is implemented as a game interface, completing the game operation on the game interface; when the task interface is implemented as an identity authentication interface, completing the identity authentication on the identity authentication interface; when the task interface is implemented as a recharge interface, completing the recharge operation on the recharge interface; and so on.

[0030] In order to address the technical problem that users need to frequently manually configure routing rules, which is cumbersome and has low configuration efficiency, in an embodiment of the present application, the terminal device scans the service code to obtain link information, which includes the server identification information and configuration indicator bound to the service code; the terminal device sends a routing configuration request, which is forwarded to the configuration node via the reverse proxy node under the instruction of the configuration indicator; the configuration node configures corresponding routing rules for the reverse proxy node based on the identification code of the terminal device and the identification information of the server bound to the service code, so that the reverse proxy node can route the service access request from the terminal device to the server bound to the service code based on the configured routing rules, thereby reducing the cumbersome operations that testers need to frequently manually configure by configuring the access to the link information obtained by scanning the code, simplifying the operation, improving the configuration efficiency, and thus improving the testing efficiency.

[0031] The following describes in detail the technical solutions provided by various embodiments of the present application in conjunction with the accompanying drawings.

[0032] Figure 1 An interactive flow chart of a server access method provided for an exemplary embodiment of the present application. In this embodiment, the interactive process involves a terminal device a1, a reverse proxy node a2, a configuration node a3, and multiple servers. For example, the multiple servers are N servers, where N ≥ 2 and N is a natural number. The reverse proxy node a2 refers to a proxy server located in front of the configuration node a3 and the N servers. The reverse proxy node a2 intercepts the request from the terminal device a1 and sends the request to the corresponding server according to the routing rules configured by the configuration node a3, so as to obtain resources from the server and return them to the terminal device a3.

[0033] In this embodiment, the specific implementation of the terminal device and server is not limited. For example, the terminal device can be implemented as an electronic device such as a desktop computer, laptop computer, smartphone, or IoT device. Correspondingly, the server can be a service-side device such as a conventional server, cloud server, or server array. In some embodiments, the configuration node can be a server. The specific implementation of the server can be referred to above.

[0034] In this embodiment, at least one service code is pre-generated. Optionally, the service code may be implemented in forms including, but not limited to, a QR code and a barcode. Each service code includes a link message, each link message including identification information of at least one server. The identification information of each server is different and serves as a unique identifier for each server among the N servers.

[0035] In this embodiment, since the link information in each service code includes the identification information of at least one server, assuming that the at least one server is n servers, where 1 ≤ n ≤ N, and n is a natural number, the correspondence between each service code and the identification information of at least one server is referred to as binding each service code with the identification information of at least one server. For ease of description, in subsequent embodiments, the binding of "each service code with the identification information of at least one server" will be referred to as simply "binding each service code with at least one server."

[0036] In this embodiment, each link information includes the identification information of the n servers bound to the service code, as well as the access address and configuration indicator of the reverse proxy node. The configuration indicator is used to direct the reverse proxy node to the configuration node, which then configures routing rules. The reverse proxy node then uses these configured routing rules to route requests from terminal devices to the server bound to the service code, thereby reducing the need for users to manually configure routing rules and improving configuration efficiency. This process is described in detail below.

[0037] In this embodiment, the terminal device refers to the terminal device of the target user. The target user can be, but is not limited to, a developer or tester. In this embodiment, see Figure 1 In step S11, the terminal device responds to the terminal device's scanning operation on the target service code and parses the target link information from the target service code. The target service code is any service code selected from at least one service code, and the server bound to the target service code is called the target server. Figure 1As shown, it includes target server b1 and target server b2. Therefore, in this embodiment, the target link information includes the access address of the reverse proxy node, the configuration node indicator, and at least one target server bound to the target service code. The configuration node indicator is used by the reverse proxy node to direct requests from terminal devices to the configuration node.

[0038] In this embodiment, the terminal device sends two types of requests to the reverse proxy node based on the target link information. One type is a routing configuration request carrying a configuration indicator. This routing configuration request is forwarded by the reverse proxy node to the configuration node, which then configures the target routing rules on the reverse proxy node for the terminal device. This allows the reverse proxy node to route another type of request from the terminal device, namely, a service access request, to at least one target server based on the configured target routing rules. The service access request is used to access at least one target server and can be either a read request or a write request. The following describes routing configuration requests and service access requests in detail, respectively, in conjunction with the interaction flow chart.

[0039] In case of getting target link information, see Figure 1 As shown in S12, the terminal device may generate a routing configuration request according to the target link information, wherein the routing configuration request includes at least a configuration node indicator and identification information of at least one target server.

[0040] Further, see Figure 1 As shown in S13 in FIG, the terminal device sends a routing configuration request to the reverse proxy node according to the access address of the reverse proxy node. Figure 1 As shown in S14 , when the reverse proxy node receives the routing configuration request sent by the terminal device, it forwards the routing configuration request to the configuration node according to the instruction of the configuration node indicator.

[0041] Furthermore, when the configuration node receives the routing configuration request sent by the reverse proxy node, it configures the target routing rule for the reverse proxy node. Figure 1 As shown in S15, the identification code of the terminal device is determined. Optionally, the specific implementation of the identification code of the terminal device is not limited, including but not limited to UUID (Universally Unique Identifier), MAC address (Media Access Control Address), and IP address (Internet Protocol Address).

[0042] Further, see Figure 1As shown in S16, the configuration node configures at least one target routing rule for the reverse proxy node based on the identification code and the identification information of at least one target server. For example, a mapping relationship between each target server and the identification code can be established as a target routing rule, and each target routing rule includes the identification information of a target server and the identification code of the terminal device.

[0043] In this embodiment, see Figure 1 As shown in S17, the reverse proxy node obtains routing rules from the configuration node. The method for obtaining these rules is not limited. For example, after generating at least one target routing rule, the configuration node may send the target routing rule to the reverse proxy node. For another example, the reverse proxy node may periodically retrieve the target routing rules generated by the configuration node from the configuration node.

[0044] In some cases, when the reverse proxy node is acquiring routing rules from the configuration node, at least one target routing rule may not be configured or not fully configured, and thus the reverse proxy node may fail to acquire the at least one target routing rule. Accordingly, if the configuration is complete, the reverse proxy node can successfully acquire the at least one target routing rule.

[0045] Optionally, when the reverse proxy node obtains the target routing rule, it returns a response to the terminal device to notify the terminal device that a service access request for at least one target server can be initiated.

[0046] In this embodiment, see Figure 1 As shown in S18, the terminal device sends a server access request to the reverse proxy node according to the access address of the reverse proxy node. When the terminal device sends a service access request, the service access request will carry the identification code of the terminal device. When the reverse proxy node receives the service access request sent by the terminal device, if it determines at least one target routing rule based on the identification code, see Figure 1 As shown in S181, the server access request is forwarded to at least one target server according to at least one target routing rule. Optionally, the determination method includes: matching the identification code of the terminal device with the identification code in the existing routing rules on the reverse proxy node; wherein the existing routing rules are all routing rules currently obtained from the configuration node.

[0047] Optionally, after completing the access to at least one target server, see Figure 1 As shown in S191, the target server may return the access result to the reverse proxy node. Figure 1 As shown in S110 , the reverse proxy node returns the access result to the terminal device.

[0048] In an embodiment of the present application, a terminal device scans a service code to obtain link information, which includes server identification information and a configuration indicator bound to the service code; the terminal device sends a routing configuration request, which is forwarded to the configuration node via the reverse proxy node under the instruction of the configuration indicator; the configuration node configures corresponding routing rules for the reverse proxy node based on the identification code of the terminal device and the identification information of the server bound to the service code, so that the reverse proxy node can route the service access request from the terminal device to the server bound to the service code based on the configured routing rules, thereby configuring routing rules for access to the link information scanned out, reducing the tedious operations that testers need to frequently manually configure, simplifying the operation, improving configuration efficiency, and thereby improving testing efficiency.

[0049] Optionally, before the terminal device responds to the scanning operation of the target service code, at least one pre-generated service code is provided to a user of the terminal device. The user may be a developer or a tester, and this is not limited.

[0050] In this embodiment, the method for providing the service code is not limited. For example, it includes, but is not limited to, displaying at least one service code on a screen carrier or a non-screen carrier. A screen carrier refers to a screen that carries information; a non-screen carrier refers to other information carriers other than a screen carrier, including, but not limited to, paper, cards, and labels.

[0051] In an optional embodiment, before the terminal device responds to a scan operation for a target service code, the method further includes: selecting a target service code from at least one pre-generated service code. The method for selecting the target service code is not limited. In some embodiments, the target service code is selected from the at least one service code based on each user's access requirements. Each user's access requirements refer to each user needing to access at least some of N servers, which may be one or more servers. In this embodiment, during the process of selecting the target service code from the at least one service code based on the access requirements, the at least one target server bound to the target service code must include at least some of the servers in the access requirements, meaning that the target service code can satisfy the user's access requirements. Optionally, to facilitate user selection, along with providing the at least one service code, identification information for the n servers bound to each service code may also be provided. Optionally, the server identification information includes, but is not limited to, the server's IP address, identification information for the physical cluster in which the server resides, and the server's operating environment. The operating environment includes, but is not limited to, the type of operating system running on the server and the version of the target application. The target application refers to the application on the target server that the user needs to access.

[0052] In other embodiments, the access requirements of each user may be known in advance, and based on the access requirements of each user, a service code that satisfies the access requirements may be directly provided to each user as a target service code.

[0053] In this embodiment, the terminal device sends a routing configuration request to the configuration node via the reverse proxy node based on the target service code. Upon receiving the configuration request from the terminal device, the configuration node determines an identification code for the terminal device. This identification code uniquely identifies the terminal device within at least one target routing rule. The embodiments of this application do not limit the manner in which the configuration node determines the identification code for the terminal device. Two optional implementations are provided below, but are not intended to be limiting.

[0054] In an optional implementation, the routing configuration request sent by the terminal device may carry identification information of the terminal device, such as but not limited to a MAC address, an IP address, etc. In this case, the identification code of the terminal device may be implemented as the identification information of the terminal device.

[0055] In another optional embodiment, if the configuration node receives a routing configuration request, it can generate an identification code for the terminal device. Furthermore, if the configuration node generates an identification code for the terminal, the identification code is returned to the terminal device via the reverse proxy node. Furthermore, upon receiving the identification code returned by the reverse proxy node, the terminal device uses the received identification code as its own identification code and can include this identification code in subsequent service access requests, allowing the reverse proxy node to determine at least one target routing rule based on the terminal device's identification code.

[0056] Optionally, if at least one target routing rule cannot be determined based on the identification code of the terminal device, the reverse proxy node will obtain a default routing rule, which corresponds to a default server. Figure 1 As shown in S182, the reverse proxy node forwards the server access request to the default server according to the default routing rule. Further, optionally, after completing the access to the default server, see Figure 1 As shown in S192, the default server can return the access result to the reverse proxy node. Figure 1 As shown in S110 , the reverse proxy node returns the access result to the terminal device.

[0057] In the embodiment of the present application, when there are multiple target servers, the target servers may be in the same physical cluster; or, they may be in different physical clusters, without limitation. The target physical cluster where each target server is located has corresponding identification information, such as, but not limited to, the name of the application deployed in the physical cluster. The target physical cluster refers to the physical cluster where the target server is located, which may be one or more. Different target physical clusters have different corresponding identification information.

[0058] In an optional embodiment, the target link information also includes identification information of the target physical cluster where each target server resides, and at least one target server corresponds to at least one target physical cluster. Accordingly, the routing configuration request generated based on the target link information includes: a configuration node indicator, identification information of at least one target server, and identification information of at least one target physical cluster.

[0059] Furthermore, in this optional embodiment, upon receiving a routing configuration request sent by the reverse proxy node, the configuration node configures at least one target routing rule for the reverse proxy node. In the process of configuring the configuration node to configure at least one target routing rule, the identification code of the terminal device may be determined first. Furthermore, based on the identification code, identification information of at least one target server, and identification information of at least one target physical cluster, at least one target routing rule is configured for the reverse proxy node. For example, by establishing a mapping relationship between the identification information of each target server and its target physical cluster and the identification code as the target routing rule for each target server, each target routing rule includes the identification information and identification code of a target server and its target physical cluster.

[0060] In this embodiment, the reverse proxy node obtains at least one configured target routing rule from the configuration node. The acquisition method is not limited and reference may be made to the above embodiment.

[0061] In this embodiment, a terminal device sends a service access request to the reverse proxy node based on the reverse proxy node's access address. The service access request carries the terminal device's identification code. Upon receiving the service access request, the reverse proxy node determines the corresponding target routing rule based on the terminal device's identification code. The target routing rule is determined by matching the terminal device's identification code with the identification codes in existing routing rules on the reverse proxy node.

[0062] If at least one target routing rule is determined according to the identification code, the server access request may be forwarded to at least one target server in at least one target physical cluster according to the at least one target routing rule.

[0063] In this embodiment, a service code generation method is provided, which is applied to a first terminal device. Figure 2 As shown, the method includes:

[0064] S201: Displaying a target page, where the target page displays identification information of multiple servers;

[0065] S202: In response to the selection operation on the multiple servers, determining at least one target server;

[0066] S203: Generate a target service code based on the identification information of at least one target server, the access address of the reverse proxy node, and the configuration node indicator, where the target service code includes target link information, and the target link information includes the access address of the reverse proxy node, the configuration node indicator, and the identification information of at least one target server; the configuration node indicator is used to point to the configuration node, and the configuration node is used to configure at least one target routing rule corresponding to the at least one target server for the reverse proxy node;

[0067] S204: Providing the target service code to the second terminal device, so that the second terminal device can access at least one target server based on a scanning operation of the target service code.

[0068] In this embodiment, the first terminal device and the second terminal device are different terminal devices. In one example, the first terminal device may be a developer's terminal device, and the second terminal device may be a tester's terminal device. In this example, the tester may be the target user in the above embodiment, and the corresponding second terminal device may be the target user's terminal device. The specific implementation of the first and second terminal devices can refer to the terminal devices in the above embodiment.

[0069] In this embodiment, a target page is displayed on the first terminal device, displaying identification information for multiple servers. Figure 3 shows an example of a target page, where the identification information for each server is its IP address. Each IP address represents one server, but this is not limited to this. For example, 10.xx.xx.170, 10.xx.xx.66, and 10.xx.xx.198 each represent a server. Optionally, the target page can also display the creators of the three servers, user r1, user r2, and user r3, respectively, as well as the corresponding creation times.

[0070] Optionally, the multiple servers may belong to different physical clusters or the same physical cluster, which is not limited. Figure 3In the example where multiple servers belong to different physical clusters, the identification information of multiple servers displayed on the target page may include identification information of different physical clusters, and the identification information corresponding to different physical clusters is different. Figure 3 As shown, the name of the application deployed on each physical cluster is used as the identification information of the physical cluster as an example, but it is not limited to this. For example, "php_webapiv1", "php_authorization", "node_admin", "hbg_java_api", "php_forgelogin" and "php_webapiv2" are the application names of different physical clusters respectively. Further, optionally, different test versions of applications can be deployed in different physical clusters; at the same time, in the same physical cluster, different test versions can also be deployed on different servers. Figure 3 As shown, numbers in the "Version" column, except for the first row, indicate the test version running in the test environment on the server in that row. For example, the server deployment corresponding to 10.xx.xx.170 runs the test version 4.55.46.1. Furthermore, the first row corresponds to the online environment where the application is deployed, also known as the baseline environment. The identification information in the first row is "api.example.com."

[0071] In this embodiment, the first terminal device determines at least one target server in response to a selection operation on multiple servers on the target page. Continuing with the above example, the first terminal device may be a developer's terminal device, and the second terminal device may be a tester's terminal device. The developer can then obtain the tester's access request and, based on the tester's access request, select at least one target server from the multiple servers. For more information on the selection method, please refer to the above embodiment.

[0072] Furthermore, a target service code is generated based on at least one target server identification information, the access address of the reverse proxy node, and the configuration node indicator. The target service code includes target link information. The target link information includes the access address of the reverse proxy node, the configuration node indicator, and the identification information of at least one target server. Figure 3As shown in the figure, "proxy.example.com" is an example of the access address of the reverse proxy node, "traefik" is an example of a configuration indicator, and "node_admin=10.xx.xx.69" and "php_webapiv1=10.xx.xx.198" are examples of identification information of different target servers and their target physical clusters, respectively. "node_admin" and "php_webapiv1" are different target physical clusters with different physical cluster identifiers. Optionally, the target link information can also include a project name, such as Figure 3 As shown in the target link information, "projectName = Project A Development Completed" represents an example of a project name.

[0073] In this embodiment, the configuration node indicator is used to point to the configuration node; the configuration node is used to configure at least one target routing rule corresponding to at least one target server for the reverse proxy node. For details about target link information and configuring target routing rules on the configuration node, please refer to the above embodiment and will not be repeated here. Optionally, when at least one target server belongs to different target physical clusters, the target link information may also include identification information of at least one target physical cluster, with different identification information corresponding to different target physical clusters.

[0074] In this embodiment, after generating a target service code, the first terminal device provides the target service code to the second terminal device, allowing the second terminal device to access at least one target server based on a scan of the target service code. For details regarding the second terminal device, refer to the above-described embodiment of the target user's terminal device accessing at least one target server, and will not be further described here.

[0075] Figure 4 A flow chart of another service access method provided by another exemplary embodiment of the present application is shown. The service access method is applied to a terminal device. Figure 4 As shown, the method includes:

[0076] S401: In response to a terminal device scanning a target service code, target link information is parsed from the target service code, where the target link information includes an access address of a reverse proxy node, a configuration node indicator, and identification information of at least one target server bound to the target service code. The configuration node indicator is used to point to a configuration node, and the configuration node is used to configure at least one target routing rule corresponding to the at least one target server for the reverse proxy node.

[0077] S402: Generate a routing configuration request according to the target link information, where the routing configuration request includes at least a configuration node indicator and identification information of at least one target server;

[0078] S403: Sending a routing configuration request to the reverse proxy node according to the access address, so that the reverse proxy node configures at least one target routing rule through the configuration node according to the configuration node indicator, where each target routing rule includes identification information of a target server and an identification code of the terminal device, where the identification code is a unique identifier of the terminal device in the target routing rule;

[0079] S404: Send a server access request to the reverse proxy node according to the access address, so that the reverse proxy node forwards the server access request to at least one target server based on the identification code and at least one target routing rule, where the server access request includes the identification code.

[0080] In an optional embodiment, before responding to the terminal device's scanning operation on the target service code, it also includes: displaying at least one service code on a screen carrier or a non-screen carrier, the at least one service code including the target service code; wherein each service code includes a link information, each link information includes the access address of the reverse proxy node, the configuration node indicator and the identification information of at least one server bound to the service code to which the link information belongs, and the identification information of at least some servers in different link information is different.

[0081] In an optional embodiment, the target service code is a QR code or a bar code.

[0082] In an optional implementation, the routing configuration request also includes: identification information of the terminal device, and the identification code of the terminal device is implemented as the identification information of the terminal device; or, the method also includes: before sending the server access request, receiving the identification code of the terminal device returned by the reverse proxy node, and the identification code of the terminal device is generated by the configuration node for the terminal device and returned to the reverse proxy node.

[0083] Figure 5 A flow chart of another routing rule configuration method provided by another exemplary embodiment of the present application. The routing configuration method is applied to configure nodes. Figure 5 As shown, the method includes:

[0084] S501: Receive a routing configuration request sent by a reverse proxy node, the routing configuration request including at least: a configuration node indicator and identification information of at least one target server bound to a target service code, the routing configuration request being generated by a terminal device based on target link information contained in the target service code, the target link information including an access address of the reverse proxy node, a configuration node indicator, and identification information of at least one target server; the configuration node indicator is used to point to the configuration node;

[0085] S502: Determine the identification code of the terminal device;

[0086] S503: Based on the identification code and identification information of at least one target server, configure at least one target routing rule for the reverse proxy node, so that the reverse proxy node forwards the server access request from the terminal device to the at least one target server according to the at least one target routing rule; each target routing rule includes identification information and an identification code of a target server.

[0087] In an optional embodiment, when determining the identification code of the terminal device, it includes: obtaining the identification information of the terminal device from the routing configuration request as the identification code; or, when receiving the routing configuration request, generating the identification code for the terminal device.

[0088] In an optional embodiment, the routing rule configuration method further includes: when the identification code is generated for the terminal, returning the identification code to the terminal device through the reverse proxy node, so that the terminal device can generate the server access request according to the identification code.

[0089] Figure 6 A flow chart of another server access method provided by another exemplary embodiment of the present application. The server access method is applied to a reverse proxy node. Figure 6 As shown, the method includes:

[0090] S601: Receive a routing configuration request sent by a terminal device, the routing configuration request including a configuration node indicator and identification information of at least one target server bound to a target service code; the routing configuration request is generated by the terminal device based on target link information contained in the target service code, the target link information including an access address of a reverse proxy node, a configuration node indicator, and identification information of at least one target server; the configuration node indicator is used to point to a configuration node, and the configuration node is used to configure at least one target routing rule corresponding to the at least one target server for the reverse proxy node;

[0091] S602: Forwarding the routing configuration request to the configuration node, so that the configuration node configures at least one target routing rule; each target routing rule includes identification information of a target server and an identification code of a terminal device;

[0092] S603: Receive a server access request sent by the terminal device, where the service access request includes an identification code;

[0093] S604: If at least one target routing rule is determined according to the identification code, the server access request is forwarded to at least one target server according to the at least one target routing rule.

[0094] In an optional embodiment, the service access method further includes: if the at least one target routing rule cannot be determined based on the identification code, obtaining a default routing rule, the default routing rule corresponding to a default server; and forwarding the server access request to the default server according to the default routing rule.

[0095] The detailed implementation and beneficial effects of each step in the method of this embodiment have been described in detail in the aforementioned embodiments and will not be elaborated here.

[0096] It should be noted that the execution entity of each step of the method provided in the above embodiment can be the same device, or the method can be executed by different devices. For example, the execution entity of steps 501 to 503 can be device A; for another example, the execution entity of steps 501 and 502 can be device A, and the execution entity of step 503 can be device B; and so on.

[0097] In addition, in some of the processes described in the above embodiments and the accompanying drawings, multiple operations that appear in a specific order are included, but it should be clearly understood that these operations may not be executed in the order in which they appear in this article or may be executed in parallel. The sequence numbers of the operations, such as 501, 502, etc., are only used to distinguish between different operations, and the sequence numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed in sequence or in parallel. It should be noted that the descriptions of "first", "second", etc. in this article are used to distinguish different messages, devices, modules, etc., and do not represent the order of precedence, nor do they limit "first" and "second" to be different types.

[0098] Figure 7 This is a structural diagram of an electronic device provided by another exemplary embodiment of the present application. Figure 7 As shown, the electronic device includes a memory 74 and a processor 75 .

[0099] The memory 74 is used to store computer programs and can be configured to store various other data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on the electronic device, contact data, phone book data, messages, pictures, videos, etc.

[0100] The memory 74 can be implemented by any type of volatile or non-volatile memory device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0101] The processor 75 is coupled to the memory 74 and is used to execute the computer program in the memory 74, so as to: in response to the terminal device scanning operation of the target service code, parse the target link information from the target service code, the target link information including the access address of the reverse proxy node, the configuration node indicator and the identification information of at least one target server bound to the target service code, the configuration node indicator is used to point to the configuration node, and the configuration node is used to configure at least one target routing rule corresponding to the at least one target server for the reverse proxy node; generate a routing configuration request according to the target link information, the routing configuration request including at least the configuration node indicator and the at least one target server. identification information of the target server; sending the routing configuration request to the reverse proxy node according to the access address, so that the reverse proxy node configures the at least one target routing rule through the configuration node according to the configuration node indicator, each target routing rule includes the identification information of a target server and the identification code of the terminal device, and the identification code is the unique identity identifier of the terminal device in the target routing rule; sending a server access request to the reverse proxy node according to the access address, so that the reverse proxy node forwards the server access request to the at least one target server based on the at least one target routing rule according to the identification code, and the service access request includes the identification code.

[0102] In an optional embodiment, before responding to the terminal device's scanning operation for the target service code, the processor 75 is further used to: display at least one service code on a screen carrier or a non-screen carrier, the at least one service code including the target service code; wherein each service code includes a link information, each link information includes an access address of a reverse proxy node, a configuration node indicator, and identification information of at least one server bound to the service code to which the link information belongs, and the identification information of at least some servers in different link information is different.

[0103] In an optional embodiment, the target service code is a QR code or a bar code.

[0104] In an optional embodiment, the routing configuration request also includes: identification information of the terminal device, and the identification code of the terminal device is implemented as the identification information of the terminal device; or, the processor 75 is further used to: before sending the server access request, receive the identification code of the terminal device returned by the reverse proxy node, and the identification code of the terminal device is generated by the configuration node for the terminal device and returned to the reverse proxy node.

[0105] Further, if Figure 7As shown, the electronic device also includes: a communication component 76, a display 77, a power component 78, an audio component 79 and other components. Figure 7 Only some components are shown schematically, which does not mean that the electronic device only includes Figure 7 In addition, Figure 7 The components in the dotted box are optional components, not mandatory components, and the specific components may depend on the product form of the electronic device. The electronic device of this embodiment can be implemented as a terminal device such as a desktop computer, a laptop computer, a smart phone or an IOT device, or a server device such as a conventional server, a cloud server or a server array. If the electronic device of this embodiment is implemented as a terminal device such as a desktop computer, a laptop computer, a smart phone, etc., it may include Figure 7 If the electronic device of this embodiment is implemented as a conventional server, cloud server or server array and other server-side devices, it may not include Figure 7 Components within the dotted box.

[0106] The embodiment of the present application also provides an electronic device, the implementation structure of the electronic device is similar to Figure 7 The implementation structure of the electronic device shown is the same or similar, and can be referred to Figure 7 The electronic device provided in this embodiment is implemented as follows: Figure 7 The difference between the electronic devices in the illustrated embodiments lies primarily in the different functions implemented by the processors in the electronic devices executing the computer programs stored in the memory. For the electronic device provided in this embodiment, the processor executes the computer program stored in the memory and is configured to: receive a routing configuration request sent by a reverse proxy node, the routing configuration request comprising at least: a configuration node indicator and identification information of at least one target server bound to a target service code; the routing configuration request is generated by a terminal device based on target link information contained in the target service code, the target link information comprising the access address of the reverse proxy node, the configuration node indicator, and identification information of the at least one target server; the configuration node indicator is used to point to the configuration node; determine an identification code of the terminal device; and configure at least one target routing rule for the reverse proxy node based on the identification code and the identification information of the at least one target server, so that the reverse proxy node forwards server access requests from the terminal device to the at least one target server according to the at least one target routing rule; each target routing rule comprises identification information of a target server and the identification code.

[0107] In an optional embodiment, when determining the identification code of the terminal device, the processor is specifically used to: obtain the identification information of the terminal device from the routing configuration request as the identification code; or, upon receiving the routing configuration request, generate the identification code for the terminal device.

[0108] In an optional embodiment, the processor is further configured to: when generating the identification code for the terminal, return the identification code to the terminal device via the reverse proxy node, so that the terminal device can generate the server access request according to the identification code.

[0109] The embodiment of the present application also provides an electronic device, the implementation structure of the electronic device is similar to Figure 7 The implementation structure of the electronic device shown is the same or similar, and can be referred to Figure 7 The electronic device provided in this embodiment is implemented as follows: Figure 7 The difference between the electronic devices in the illustrated embodiments mainly lies in that the functions implemented by the processors in the electronic devices when executing the computer programs stored in the memories are different. For the electronic device provided in this embodiment, its processor executes a computer program stored in a memory, and can be used to: receive a routing configuration request sent by a terminal device, the routing configuration request including a configuration node indicator and identification information of at least one target server bound to a target service code; the routing configuration request is generated by the terminal device based on target link information contained in the target service code, the target link information including the access address of the reverse proxy node, the configuration node indicator, and identification information of the at least one target server, the configuration node indicator is used to point to a configuration node, and the configuration node is used to configure at least one target routing rule corresponding to the at least one target server for the reverse proxy node; forward the routing configuration request to the configuration node for the configuration node to configure the at least one target routing rule; each target routing rule includes identification information of a target server and an identification code of the terminal device; receive a server access request sent by the terminal device, the service access request including the identification code; if the at least one target routing rule is determined based on the identification code, forward the server access request to the at least one target server based on the at least one target routing rule.

[0110] In an optional embodiment, the processor is further configured to: if the at least one target routing rule cannot be determined based on the identification code, obtain a default routing rule, the default routing rule corresponding to a default server; and forward the server access request to the default server based on the default routing rule.

[0111] The embodiment of the present application also provides an electronic device, the implementation structure of the electronic device is similar to Figure 7 The implementation structure of the electronic device shown is the same or similar, and can be referred to Figure 7 The electronic device provided in this embodiment is implemented as follows: Figure 7 The difference between the electronic devices in the illustrated embodiments lies primarily in the different functions implemented by the processors in the electronic devices executing the computer programs stored in the memory. For the electronic device provided in this embodiment, the processor executes the computer program stored in the memory and is configured to: display a target page displaying identification information of multiple servers; determine at least one target server in response to a selection operation on the multiple servers; generate a target service code based on the identification information of the at least one target server, the access address of the reverse proxy node, and a configuration node indicator, the target service code including target link information, the target link information including the access address of the reverse proxy node, the configuration node indicator, and the identification information of the at least one target server; the configuration node indicator is used to point to a configuration node, the configuration node being used to configure at least one target routing rule corresponding to the at least one target server for the reverse proxy node; and provide the target service code to a second terminal device so that the second terminal device can access the at least one target server based on a scanning operation of the target service code.

[0112] Figure 8 This is a schematic diagram of the structure of a server access device provided by an exemplary embodiment of the present application. Figure 8 As shown, the service access device 80 includes: a parsing module 81 , a generating module 82 and a sending module 83 .

[0113] The parsing module 81 is configured to parse target link information from the target service code in response to a scanning operation of the target service code by the terminal device, wherein the target link information includes an access address of a reverse proxy node, a configuration node indicator, and identification information of at least one target server bound to the target service code, wherein the configuration node indicator is used to point to a configuration node, and the configuration node is used to configure at least one target routing rule corresponding to the at least one target server for the reverse proxy node;

[0114] A generating module 82, configured to generate a routing configuration request according to the target link information, wherein the routing configuration request includes at least the configuration node indicator and identification information of the at least one target server;

[0115] a sending module 83, configured to send the routing configuration request to the reverse proxy node according to the access address, so that the reverse proxy node configures the at least one target routing rule through the configuration node according to the configuration node indicator, where each target routing rule includes identification information of a target server and an identification code of the terminal device, where the identification code is a unique identifier of the terminal device in the target routing rule;

[0116] The sending module 83 is also used to send a server access request to the reverse proxy node according to the access address, so that the reverse proxy node forwards the server access request to the at least one target server based on the identification code of the terminal device and the at least one target routing rule, and the service access request includes the identification code of the terminal device.

[0117] In an optional embodiment, before responding to the terminal device's scanning operation on the target service code, the parsing module 81 is further used to: display at least one service code on a screen carrier or a non-screen carrier, and the at least one service code includes the target service code; wherein each service code includes a link information, and each link information includes the access address of the reverse proxy node, the configuration node indicator and the identification information of at least one server bound to the service code to which the link information belongs, and the identification information of at least some servers in different link information is different.

[0118] In an optional embodiment, the target service code is a QR code or a bar code.

[0119] In an optional embodiment, the routing configuration request also includes: identification information of the terminal device, and the identification code of the terminal device is implemented as the identification information of the terminal device; or, the sending module 83 is also used to: before sending the server access request, receive the identification code of the terminal device returned by the reverse proxy node, and the identification code of the terminal device is generated by the configuration node for the terminal device and returned to the reverse proxy node.

[0120] Figure 9 This is a schematic diagram of a routing rule configuration device provided by an exemplary embodiment of the present application. Figure 9 As shown, the routing rule configuration device 90 includes: a receiving module 91 , a determining module 92 and a configuring module 93 .

[0121] The receiving module 91 is configured to receive a routing configuration request sent by a reverse proxy node, the routing configuration request including at least: a configuration node indicator and identification information of at least one target server bound to a target service code; the routing configuration request is generated by a terminal device based on target link information contained in the target service code, the target link information including the access address of the reverse proxy node, the configuration node indicator, and identification information of the at least one target server; the configuration node indicator is used to point to the configuration node;

[0122] A determination module 92, configured to determine an identification code of the terminal device;

[0123] Configuration module 93 is used to configure at least one target routing rule for the reverse proxy node based on the identification code and the identification information of the at least one target server, so that the reverse proxy node forwards the server access request from the terminal device to the at least one target server according to the at least one target routing rule; each target routing rule includes the identification information of a target server and the identification code.

[0124] In an optional embodiment, when determining the identification code of the terminal device, the determination module 92 is specifically used to: obtain the identification information of the terminal device from the routing configuration request as the identification code; or, upon receiving the routing configuration request, generate the identification code for the terminal device.

[0125] In an optional embodiment, the configuration module 93 is further configured to: when generating the identification code for the terminal, return the identification code to the terminal device via the reverse proxy node, so that the terminal device can generate the server access request according to the identification code.

[0126] Figure 10 This is a schematic diagram of the structure of a server access device provided by an exemplary embodiment of the present application. Figure 10 As shown, the service access device 100 includes a receiving module 101 and a forwarding module 102 .

[0127] The receiving module 101 is configured to receive a routing configuration request sent by a terminal device, the routing configuration request including a configuration node indicator and identification information of at least one target server bound to a target service code; the routing configuration request is generated by the terminal device based on target link information contained in the target service code, the target link information including an access address of the reverse proxy node, the configuration node indicator, and identification information of the at least one target server; the configuration node indicator is used to point to a configuration node, and the configuration node is used to configure at least one target routing rule corresponding to the at least one target server for the reverse proxy node;

[0128] Forwarding module 102, configured to forward the routing configuration request to the configuration node, so that the configuration node configures the at least one target routing rule; each target routing rule includes identification information of a target server and an identification code of the terminal device;

[0129] The receiving module 101 is further configured to receive a server access request sent by the terminal device, wherein the server access request includes the identification code;

[0130] The forwarding module 102 is further configured to forward the server access request to the at least one target server according to the at least one target routing rule if the at least one target routing rule is determined according to the identification code.

[0131] In an optional embodiment, the forwarding module 102 is further used to: if the at least one target routing rule cannot be determined according to the identification code, obtain a default routing rule, the default routing rule corresponding to a default server; and forward the server access request to the default server according to the default routing rule.

[0132] Figure 11 This is a schematic diagram of a service code generating device provided by an exemplary embodiment of the present application. Figure 11 As shown, the service code generating device 111 includes: a display module 112 , a determination module 113 , a generation module 114 and a sending module 115 .

[0133] The display module 112 is used to display a target page, wherein the target page displays identification information of multiple servers;

[0134] a determination module 113, configured to determine at least one target server in response to a selection operation on the plurality of servers;

[0135] A generating module 114 is configured to generate a target service code based on the identification information of the at least one target server, the access address of the reverse proxy node, and the configuration node indicator, wherein the target service code includes target link information, the target link information includes the access address of the reverse proxy node, the configuration node indicator, and the identification information of the at least one target server; the configuration node indicator is used to point to a configuration node, and the configuration node is used to configure at least one target routing rule corresponding to the at least one target server for the reverse proxy node;

[0136] The sending module 115 is configured to provide the target service code to the second terminal device, so that the second terminal device can access the at least one target server based on a scanning operation of the target service code.

[0137] The above-mentioned memory can be implemented by any type of volatile or non-volatile memory device or a combination thereof, such as static random-access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0138] The above-mentioned communication component is configured to facilitate wired or wireless communication between the device where the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G / LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra wide band (UWB) technology, Bluetooth (BT) technology and other technologies.

[0139] The above-mentioned display includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor can not only sense the boundary of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

[0140] The power supply assembly provides power to various components of the device in which the power supply assembly is located. The power supply assembly may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device in which the power supply assembly is located.

[0141] The above-mentioned audio component can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC), and when the device where the audio component is located is in an operating mode, such as call mode, recording mode, and voice recognition mode, the microphone is configured to receive external audio signals. The received audio signal can be further stored in a memory or sent via a communication component. In some embodiments, the audio component also includes a speaker for outputting audio signals.

[0142] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to magnetic disk storage, compact disc read-only memory (CD-ROM), optical storage, etc.) that contain computer-usable program code.

[0143] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0144] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0145] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0146] In a typical configuration, a computing device includes one or more processors (Central Processing Unit, CPU), input / output interfaces, network interfaces, and memory.

[0147] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0148] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be used to store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change random access memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media such as modulated data signals and carrier waves.

[0149] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0150] The above are merely embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.

Claims

1. A server access method, characterized in that: Applied to a terminal device, the method includes: In response to a scanning operation of the target service code by the terminal device, target link information is parsed from the target service code, the target link information including an access address of a reverse proxy node, a configuration node indicator, and identification information of at least one target server bound to the target service code, the configuration node indicator being used to point to a configuration node, and the configuration node being used to configure at least one target routing rule corresponding to the at least one target server for the reverse proxy node; generating a routing configuration request according to the target link information, wherein the routing configuration request includes at least the configuration node indicator and identification information of the at least one target server; Sending the routing configuration request to the reverse proxy node according to the access address, so that the reverse proxy node configures the at least one target routing rule through the configuration node according to the configuration node indicator, where each target routing rule includes identification information of a target server and an identification code of the terminal device, where the identification code is a unique identifier of the terminal device in the target routing rule; A server access request is sent to the reverse proxy node according to the access address, so that the reverse proxy node forwards the server access request to the at least one target server based on the identification code and the at least one target routing rule, wherein the service access request includes the identification code.

2. The method according to claim 1, characterized in that Before responding to the terminal device scanning the target service code, the method further includes: displaying at least one service code on a screen carrier or a non-screen carrier, wherein the at least one service code includes the target service code; Among them, each service code includes a link information, each link information includes the access address of the reverse proxy node, the configuration node indicator and the identification information of at least one server bound to the service code to which the link information belongs, and the identification information of at least some servers in different link information is different.

3. The method according to claim 1, characterized in that The target service code is a QR code or a bar code.

4. The method according to any one of claims 1 to 3, characterized in that The routing configuration request further includes: identification information of the terminal device, where the identification code of the terminal device is implemented as the identification information of the terminal device; or The method further includes: before sending the server access request, receiving an identification code of the terminal device returned by the reverse proxy node, where the identification code of the terminal device is generated by the configuration node for the terminal device and returned to the reverse proxy node.

5. A routing rule configuration method, characterized in that: Applied to configuring a node, the method includes: receiving a routing configuration request sent by a reverse proxy node, the routing configuration request including at least: a configuration node indicator and identification information of at least one target server bound to a target service code, the routing configuration request being generated by a terminal device based on target link information contained in the target service code, the target link information including an access address of the reverse proxy node, the configuration node indicator, and identification information of the at least one target server; the configuration node indicator being used to point to the configuration node; Determining an identification code of the terminal device; Based on the identification code and the identification information of the at least one target server, at least one target routing rule is configured for the reverse proxy node, so that the reverse proxy node forwards the server access request from the terminal device to the at least one target server according to the at least one target routing rule; each target routing rule includes the identification information of a target server and the identification code.

6. The method according to claim 5, characterized in that Determining the identification code of the terminal device includes: Acquire identification information of the terminal device from the routing configuration request as the identification code; or Upon receiving the routing configuration request, the identification code is generated for the terminal device.

7. The method according to claim 6, characterized in that Also includes: When the identification code is generated for the terminal, the identification code is returned to the terminal device through the reverse proxy node, so that the terminal device can generate the server access request according to the identification code.

8. A server access method, characterized in that: Applied to a reverse proxy node, the method includes: receiving a routing configuration request sent by a terminal device, the routing configuration request including a configuration node indicator and identification information of at least one target server bound to a target service code; the routing configuration request is generated by the terminal device based on target link information contained in the target service code, the target link information including an access address of the reverse proxy node, the configuration node indicator, and identification information of the at least one target server, the configuration node indicator being used to point to a configuration node, and the configuration node being used to configure at least one target routing rule corresponding to the at least one target server for the reverse proxy node; Forwarding the routing configuration request to the configuration node so that the configuration node configures the at least one target routing rule; each target routing rule includes identification information of a target server and an identification code of the terminal device; receiving a server access request sent by the terminal device, wherein the service access request includes the identification code; If the at least one target routing rule is determined according to the identification code, the server access request is forwarded to the at least one target server according to the at least one target routing rule.

9. The method according to any one of claim 8, characterized in that Also includes: If the at least one target routing rule cannot be determined according to the identification code, obtaining a default routing rule, the default routing rule corresponding to a default server; According to the default routing rule, the server access request is forwarded to the default server.

10. A method for generating a service code, characterized in that: Applied to a first terminal device, the method includes: Displaying a target page, wherein the target page displays identification information of multiple servers; In response to the selection operation on the plurality of servers, determining at least one target server; Generate a target service code based on the identification information of the at least one target server, the access address of the reverse proxy node, and the configuration node indicator, wherein the target service code includes target link information, and the target link information includes the access address of the reverse proxy node, the configuration node indicator, and the identification information of the at least one target server; the configuration node indicator is used to point to a configuration node, and the configuration node is used to configure at least one target routing rule corresponding to the at least one target server for the reverse proxy node; The target service code is provided to a second terminal device, so that the second terminal device can access the at least one target server based on a scanning operation of the target service code.

11. An electronic device, characterized in that: The method comprises a memory and a processor, wherein the memory is used to store a computer program, and the processor is coupled to the memory and is used to execute the computer program to implement the steps in the method according to any one of claims 1 to 4, claims 5 to 7, claims 8 to 9, and claim 10.

12. A computer-readable storage medium storing a computer program / instruction, characterized in that: When the computer program is executed by a processor, the processor is enabled to implement the steps of the method according to any one of claims 1 to 4, 5 to 7, 8 to 9 and 10.

13. A computer program product, characterized in that include: A computer program / instruction, when executed by a processor, causes the processor to implement the steps of the method according to any one of claims 1 to 4, claims 5 to 7, claims 8 to 9 and claim 10.

Images