CN113761400A - Access request forwarding method, device and equipment - Google Patents

Abstract

The embodiment of the specification discloses an access request forwarding method, a device and equipment, and the scheme comprises the following steps: acquiring an access request containing a target uniform resource locator through an SLB server; the target uniform resource locator at least comprises a target domain name and a target path; and according to a mapping relation table generated based on the supportable uniform resource locator of the registered application server, inquiring a target application server corresponding to the target uniform resource locator so as to forward the access request to the target application server for processing.

Description

An access request forwarding method, device and device

technical field

The present application relates to the field of computer technologies, and in particular, to a method, apparatus, and device for forwarding an access request.

Background technique

At present, in the field of computer technology, the number of back-end applications deployed on servers is increasing. After many access requests are forwarded to the server where the backend application is deployed (hereinafter referred to as "application server"), the application server also needs to identify the access request forwarded to itself to determine whether the access request is a request that it can process.

When the access request reaches a certain number, the process of identifying the access request will occupy a high amount of resources of the application server. Especially with the rise of functions such as cloud native, functions such as cloud native also consume a lot of processing resources of application servers.

Therefore, how to reduce the resource consumption of the application server in identifying the access request has become a technical problem to be solved urgently by those skilled in the art.

SUMMARY OF THE INVENTION

The embodiments of this specification provide an access request forwarding method, apparatus, and device, so as to reduce the resource consumption of the application server in identifying the access request.

In order to solve the above-mentioned technical problems, the embodiments of this specification are implemented as follows:

A method for forwarding an access request based on an SLB server provided by an embodiment of this specification includes:

The SLB server obtains an access request containing a target uniform resource locator; the target uniform resource locator at least contains a target domain name and a target path;

According to the mapping relationship table, query the target application server corresponding to the target uniform resource locator; the mapping relationship table is generated based on the registration information of the registered application server, and the registration information includes the supportable uniform resources of the registered application server Locator; the supportable uniform resource locator at least includes a domain name and a path;

The access request is forwarded to the target application server.

A method for processing an access request provided by an embodiment of this specification includes:

The application server obtains the access request forwarded by the SLB server; the access request is that the SLB server based on the access request containing the target uniform resource locator, according to the mapping table, finds that the target application server corresponding to the target uniform resource locator is: After the application server, the access request is forwarded to the application server; the target uniform resource locator at least includes a target domain name and a target path;

The application server determines whether the access request is an access request supported by the application server based on the filtering rule pre-stored by the application server;

if so, process the access request;

Otherwise, the access request is denied.

An access request forwarding device provided by the embodiments of this specification, applied to an SLB server, includes:

an obtaining module for obtaining an access request including a target uniform resource locator; the target uniform resource locator at least includes a target domain name and a target path;

a query module, configured to query the target application server corresponding to the target uniform resource locator according to a mapping relationship table; the mapping relationship table is generated based on the registration information of the registration application server, and the registration information includes the registration application server The supportable uniform resource locator; the supportable uniform resource locator at least includes a domain name and a path;

A forwarding module, configured to forward the access request to the target application server.

An apparatus for processing an access request provided by an embodiment of this specification, applied to an application server, includes:

The acquiring module is used to acquire the access request forwarded by the SLB server; the access request is that the SLB server queries the target corresponding to the target uniform resource locator based on the access request containing the target uniform resource locator according to the mapping table After the application server is the application server, it forwards the access request to the application server; the target uniform resource locator at least includes a target domain name and a target path;

a judgment module, configured to judge whether the access request is an access request supported by the application server based on the filtering rules pre-stored by the application server, and obtain a judgment result;

an access request processing module, configured to process the access request when the judgment result indicates that the access request is an access request supported by the application server;

An access rejection module, configured to reject the access request when the judgment result indicates that the access request is not an access request supported by the application server.

An access request forwarding device provided by an embodiment of this specification includes:

at least one processor; and,

a memory communicatively coupled to the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

Obtain an access request containing a target uniform resource locator; the target uniform resource locator at least contains a target domain name and a target path;

According to the mapping relationship table, query the target application server corresponding to the target uniform resource locator; the mapping relationship table is generated based on the registration information of the registered application server, and the registration information includes the supportable uniform resources of the registered application server Locator; the supportable uniform resource locator at least includes a domain name and a path;

The access request is forwarded to the target application server.

An access request processing device provided by an embodiment of this specification includes:

at least one processor; and,

a memory communicatively coupled to the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

Obtain the access request forwarded by the SLB server; the access request is that the SLB server based on the access request containing the target uniform resource locator, according to the mapping relationship table, finds that the target application server corresponding to the target uniform resource locator is the After the device is installed, the access request is forwarded to the device; the target uniform resource locator at least includes the target domain name and the target path;

Judging whether the access request is an access request supported by the device based on the filtering rules pre-stored by the device;

if so, process the access request;

Otherwise, the access request is denied.

At least one embodiment in this specification can achieve the following beneficial effects:

By making the SLB server forward the obtained access request containing the target uniform resource locator to the support server according to the mapping relationship table that records the mapping relationship between the supportable uniform resource locator of the registered application server and the identifier of the registered application server The processing is performed at the target application server that processes the access request, so that the target application server does not need to identify whether it supports the processing of the access request, so as to reduce the resource consumption of the application server in identifying the access request.

In this solution, the target uniform resource locator in the access request can at least contain the target domain name and the target path, and the supportable uniform resource locator of the registered application server in the mapping relationship table can also contain at least the domain name and the path, so that the SLB server can The access request can be accurately forwarded to further reduce the resource consumption of the application server in identifying the access request.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present specification or the prior art, the following briefly introduces the accompanying drawings required in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments described in this application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort.

1 is a schematic flowchart of an overall solution of a method for forwarding an access request based on an SLB server in an embodiment of this specification;

2 is a schematic flowchart of a method for forwarding an access request based on an SLB server provided by an embodiment of the present specification;

3 is a schematic flowchart of a method for processing an access request provided by an embodiment of the present specification;

FIG. 4 is a schematic structural diagram of an access request forwarding apparatus corresponding to FIG. 2 provided by an embodiment of the present specification;

5 is a schematic structural diagram of an apparatus for processing an access request corresponding to FIG. 3 according to an embodiment of the present specification;

FIG. 6 is a schematic structural diagram of an access request forwarding device corresponding to FIG. 2 and an access request processing device corresponding to FIG. 3 according to an embodiment of the present specification.

Detailed ways

In order to make the objectives, technical solutions and advantages of one or more embodiments of this specification clearer, the technical solutions of one or more embodiments of this specification will be clearly and completely described below with reference to the specific embodiments of this specification and the corresponding drawings. . Obviously, the described embodiments are only some of the embodiments of the present specification, but not all of the embodiments. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments in the present specification without creative efforts fall within the protection scope of one or more embodiments of the present specification.

The technical solutions provided by the embodiments of the present specification will be described in detail below with reference to the accompanying drawings.

In the prior art, a front-end application generally refers to an application program running on a device such as a PC terminal or a mobile terminal, which can provide an application interface to a user so as to facilitate the user's operation. The back-end application refers to the application program running on the application server corresponding to the front-end application. The back-end application can interact with the database to process the corresponding business logic and assist in realizing the functions of the front-end application.

Currently, when a server in which a backend application is deployed (hereinafter referred to as an "application server") receives an access request sent by a frontend application, it usually needs to identify whether the access request is a request that it can process. When the access request reaches a certain number, the process of identifying the access request will occupy a high amount of resources of the application server. Therefore, how to reduce the resource consumption of the application server in identifying the access request has become a technical problem to be solved urgently by those skilled in the art.

To facilitate understanding of the solution in the embodiment, the SLB server is described below.

A server load balancing (Server Load Balancing, English abbreviation: SLB) server refers to a server that can distribute traffic to multiple servers in a server cluster to achieve load balancing of devices in the server cluster. In practical applications, the SLB server can perform forwarding judgment and forwarding operations on the access request based on the load balancing algorithm, so as to forward the access request to the physical server for processing.

FIG. 1 is a schematic flowchart of an overall solution of an access request forwarding method based on an SLB server in an embodiment of the specification.

As shown in FIG. 1 , the first registered application server 102 is loaded with a first application, the second registered application server 103 is loaded with a second application, and both the first application and the second application may be back-end applications. It is assumed that the first application in the first registered application server 102 supports the processing of access requests containing the uniform resource locator "http//a.cn/path1" or "http//b.com/path2", while the second application The second application in the registered application server 103 supports the

The processing of the access request of "http//a.cn/path3".

The first registered application server 102 and the second registered application server 103 may be registered with the SLB server 101 in advance, so that the SLB server 101 can generate a mapping relationship table. The mapping relationship table may record the mapping relationship between the identifier of the first registered application server 102 and the supportable uniform resource locator of the first registered application server 102, and the identifier of the second registered application server 103 and the second registered application server 103. The mapping relationship between the supportable uniform resource locators of the registration application server 103 is registered. Continuing from the previous example, the mapping relationship recorded in the mapping relationship table generated by the SLB server 101 may include: the mapping relationship between "101" and "http//a.cn/path1", and the mapping relationship between "101" and "101"

The mapping relationship between "http//b.com/path2", and the mapping relationship between "102" and "http//a.cn/path3".

Subsequently, when the SLB server 101 receives the access request, it can query the registration application server in each server in the server cluster that can process the access request according to the pre-generated mapping table, and forward the access request to the corresponding registration application server processed at the application server. For example, the first access request 104 and the second access request 105 are forwarded to the first registered application server 102 for processing, and the fourth access request 107 is forwarded to the second registered application server 103 for processing.

If the SLB server does not find a registered application server that can process the access request, it can reject the access request without forwarding the access request. For example, according to the mapping table, it is found that neither the first registered application server 102 nor the second registered application server 103 supports processing the third access request 106 , the SLB server may refuse to forward the third access request 106 .

Next, a method for forwarding an access request based on an SLB server provided by the embodiments of the specification will be described in detail with reference to the accompanying drawings:

FIG. 2 is a schematic flowchart of a method for forwarding an access request based on an SLB server according to an embodiment of the present specification. From a program perspective, the execution body of the process may be the SLB server or a program mounted in the SLB server.

As shown in Figure 2, the process can include the following steps:

Step 202: the SLB server obtains an access request including a target uniform resource locator; the target uniform resource locator at least includes a target domain name and a target path.

In the embodiment of this specification, a uniform resource locator (uniform resource locator, English abbreviation: URL) may include information such as a domain name and a path, and the uniform resource locator may be used to locate a specified resource. The domain name (Domain Name) may be composed of a string of characters separated by dots, and the domain name may be used as a locating identifier for a computer during data transmission. The path can refer to the line traversed when looking for a file. In practical applications, paths can include absolute paths and relative paths. For ease of understanding, the solution description is given by taking the target uniform resource locator as "http//a.cn/path1" as an example, wherein the domain name may be "a.cn". The absolute path can be "http//a.cn/path1", and the relative path can be "path1".

In the embodiment of this specification, the access request carrying the target uniform resource locator may be various network requests carrying the target uniform resource locator, for example, HTTP (Hyper Text Transfer Protocol) request, FTP (File Transfer Protocol) request, etc. . The access request carrying the target uniform resource locator may be used to request processing of the target resource indicated by the target uniform resource locator.

In the embodiment of this specification, the SLB server may distribute traffic to multiple servers in the server cluster, so as to achieve load balancing among the servers in the server cluster. The server in the server cluster may be a server carrying a back-end application (ie, an application server), and the application server may be used to process an access request including a target uniform resource locator generated by a front-end application or other back-end applications. In practical applications, the server cluster may include one or more physical servers, and may also include one or more virtual servers (eg, cloud servers), which are not specifically limited.

In the embodiment of this specification, when there is an access request including the target uniform resource locator that requests the server cluster to process, the SLB server can obtain the access request, and determine whether to forward the access request to the application server in the server cluster to be processed.

Step 204: Query the target application server corresponding to the target uniform resource locator according to the mapping relationship table; the mapping relationship table is generated based on the registration information of the registered application server, and the registration information includes the available information of the registered application server. Uniform resource locators are supported; the supportable uniform resource locators include at least a domain name and a path.

In the embodiment of this specification, the SLB server may forward the access request to the application server (ie, the registration application server) that has completed the registration at the SLB server. Therefore, the application server with the backend application needs to be registered with the SLB server in advance.

In the embodiment of this specification, the SLB server can obtain the registration information of the registered application server, and the registration information can include the uniform resource locator (that is, the uniform resource locator) corresponding to the resource that the registered application server can process. The SLB server may also generate, according to the registration information of the registered application server, a mapping relation table that records the mapping relation between the supported uniform resource locator of the registered application server and the identifier of the registered application server. Therefore, the SLB server can determine whether the access request obtained in step 202 is an access request that can be processed by the registered application server based on the mapping relationship table.

In the embodiment of this specification, the supportable uniform resource locator in the registration information of the registration application server may be manually set according to the actual situation. A registered application server can contain one or more domain names and one or more paths in its supportable uniform resource locator.

For example, according to the content in FIG. 1 , it can be known that the supportable uniform resource locators of the first registered application server carrying the first application include “http://a.cn/path1” and “http://b.com/path2” Wait. The supportable uniform resource locator of the second registered application server hosting the second application may include

"http//a.cn/path3" etc. That is, both the first application and the second application can process part of the access request whose domain name is "a.cn". And the first application can also support multiple domain names (for example, "a.cn",

"b.com") processing of access requests.

In practical applications, since there are many applications, there may only be slightly different front-end pages, but the back-end interface and business logic can be the same, but at present, it is usually necessary to deploy two back-end applications with the same program code on the server to support the Different front-end applications have problems of high back-end application deployment and maintenance costs.

In the embodiment of this specification, the solution in FIG. 1 enables the user to set the supportable uniform resource locator of the registered application server according to actual needs, and enables the SLB server to access the access based on the supportable uniform resource locator of the registered application server. The request is forwarded, so that a back-end application can be deployed on the server to support access requests with the same business logic sent by multiple front-end applications. For example, the first application can support access to multiple domain names (for example, "a.cn", "b.com") access requests are processed. This solution is conducive to reducing the complexity and cost of application development and post-operation and maintenance.

Step 206: Forward the access request to the target application server.

In the embodiment of this specification, when the SLB server finds that there is an application server (that is, the target application server) that can process the access request carrying the target uniform resource locator, it can forward the access request to the target application server, In order to make the target application server process and respond to the access request.

In the embodiment of this specification, when the target application server corresponding to the target uniform resource locator cannot be queried, it may indicate that none of the registered application servers at the SLB server support the processing of the access request. Therefore, the SLB server The access request can be rejected without forwarding the access request to the registered application server for identification of whether processing can be supported, so that the resource consumption of the registered application server in identifying the access request can be reduced.

It should be understood that the order of some steps in the method described in one or more embodiments of this specification may be interchanged according to actual needs, or some steps may be omitted or deleted.

The method in Fig. 2 is based on the principle that the SLB server can forward the access request to the registered application server to realize load balancing, so that the SLB server can record the supported uniform resource locator of the registered application server according to the relationship between the registered application server and the registered application server's identity. The mapping relationship table of the mapping relationship between, to forward the obtained access request containing the target uniform resource locator to the target application server that supports processing the access request for processing, so that the target application server does not need to identify whether it supports the access request. The processing of access requests to reduce the resource consumption of the application server in identifying access requests.

In this solution, the target uniform resource locator in the access request can at least contain the target domain name and the target path, and the supportable uniform resource locator of the registered application server in the mapping relationship table can also contain at least the domain name and the path, so that the SLB server can The access request can be accurately forwarded to further reduce the resource consumption of the application server in identifying the access request.

In this solution, the SLB server can be made to forward the access requests of different domain names to the registered application server carrying the specified back-end application for processing, so that the same back-end application can support the access requests of different front-end applications, which is beneficial to reduce The complexity and cost of application development and post-operation and maintenance.

Based on the method in FIG. 2 , some specific implementations of the method are also provided in the embodiments of the present specification, which will be described below.

In the embodiment of this specification, step 204: query the target application server corresponding to the target uniform resource locator, which may specifically include:

An initial target application server that supports the target domain name is queried.

If the initial target application server supporting the target domain name is not queried, reject the access request;

If an initial target application server supporting the target domain name is found, query whether the path supported by the initial target application server includes the target path.

If the path supported by the initial target application server includes the target path, the initial target application server is determined as the target application server.

If the path supported by the initial target application server does not include the target path, the access request is rejected.

In the embodiment of this specification, rejecting the access request may specifically include: the SLB server stops forwarding the access request. Therefore, the registered application server at the SLB server will not receive the access request.

In this embodiment of the present specification, after rejecting the access request, the method may further include: feeding back request failure information to the device sending the access request. Therefore, the response waiting time of the device sending the access request to the access request can be reduced.

In the embodiment of this specification, by first querying whether there is a registered application server that supports the target domain name in the target uniform resource locator, if not, the query is stopped and the access request is rejected. The exact matching query method is used, and the query efficiency is higher.

In the embodiment of this specification, since the SLB server can be used to implement load balancing of the server cluster. Therefore, step 204: querying the target application server corresponding to the target uniform resource locator may specifically include: querying the target application server cluster corresponding to the target uniform resource locator.

Before forwarding the access request to the target application server, the method may further include: determining a low load target from the target application server cluster according to real-time load indicators of each target application server in the target application server cluster An application server; the real-time load index of the low-load target application server is smaller than the real-time load index of some target application servers in the target application server cluster.

Step 206: Forwarding the access request to the target application server may specifically include: forwarding the access request to the low-load target application server.

In the embodiment of this specification, when the SLB server determines that there are multiple registered application servers (that is, target application servers) that can support the access request obtained in processing step 202, the above-mentioned multiple target application servers can be determined as the target application. A server in a server cluster.

The SLB server may determine a server with a low current load as a low-load target application server from the target application server cluster, and send the access request to the low-load target application server for processing. Therefore, on the basis of ensuring that the access request can be processed, the function of balancing the load of each server in the server cluster is realized. In the embodiments of this specification, the process of determining the low-load target application server by the SLB server is not specifically limited.

In practical applications, since the hardware resource configuration of different application servers is usually different, some application servers are more suitable for processing access requests that require high-frequency data reading and writing, while some application servers are more suitable for processing GPUs. Access requests with high resource demands.

Therefore, in order to improve the resource utilization rate of the registered application server and the processing efficiency of the access request, the registration information of the registered application server may further include a supportable interface (Application Programming Interface, English abbreviation: API) of the registered application server. In practical applications, the user can specify the supported interfaces of the application server in the registration information according to actual needs. For example, the registration information of the application server with high IO efficiency includes interfaces that require high information input and output efficiency, for example, transformAPI, the Transform API allows third-party plug-ins to operate the compiled class files before converting the class files to dex files, so as to simplify the custom operation of the class files; and the registration information of the application server with high GPU performance includes the GPU resources. Interfaces that are in high demand or require high GPU operating efficiency, such as the compressImage API for compressing images. In this way, the SLB server can forward high IO access requests to the registered application server with high IO efficiency for processing, and forward high GPU access requests to the registered application server with high GPU performance for processing, which is conducive to improving the registered application server. resource utilization and processing efficiency of access requests.

In the embodiments of the present specification, there are multiple manners for the SLB server to generate the mapping relationship table.

Method 1, when the application server registers with the SLB server:

The SLB server may acquire registration information of the registered application server; the registration information includes the supportable uniform resource locator of the registered application server.

Obtain the identifier of the registered application server.

The identifier of the registered application server and the supportable uniform resource locator of the registered application server are associated and stored in the mapping relationship table.

In this implementation manner, by enabling the SLB server to transmit the supportable uniform resource locator of the registered application server based on the registration information of the registered application server, there is no need to perform additional transmission of the supported uniform resource locator of the registered application server The steps are to reduce the transformation of the SLB server, which is beneficial to reduce the transformation cost of the access request forwarding scheme.

Method 2: Since the supported uniform resource locator of the registered application server may change, in order to improve the accuracy of the SLB server for forwarding the access request, therefore,

The SLB server can be made to obtain the update information sent by the registered application server; the updated information includes the updated supportable uniform resource locator of the registered application server.

According to the update information, the mapping relationship table is updated. For example, according to the update information, delete the mapping relationship between the uniform resource locator that is no longer supported by the registered application server and the registered application server identifier in the mapping relationship table, or add a new registered application server in the mapping relationship table. The added mapping relationship between the uniform resource locator and the registered application server identifier can be supported.

In the above implementation manner, when the supported uniform resource locator of the registered application server changes, the registered application server does not need to perform a re-registration operation at the SLB server, and the SLB service can also obtain the updated registered application server. can support uniform resource locators to update the mapping table. Therefore, it is beneficial to improve the operation stability and forwarding accuracy of the access request forwarding scheme.

In the third way, the registered application server can actively send the supported uniform resource locator to the SLB server. Besides, the SLB server can also actively request the registered application server to obtain the uniform resource locator supported by it. specific:

The SLB server may obtain the interface information of the registered application server.

Through the interface corresponding to the interface information, query the supportable uniform resource locator of the registered application server.

The identifier of the registered application server and the supportable uniform resource locator of the registered application server are associated and stored in the mapping relationship table.

In this implementation manner, the registration application server may open a specified interface for the SLB server to call, so that the SLB server obtains the supportable uniform resource locator and the updated supportable uniform resource locator of the registered application server based on the interface, Thus, the mapping relationship table is maintained to ensure the real-time and accurate mapping relationship table, thereby reducing the probability of wrong forwarding or wrong rejection of the access request.

Based on the same idea, the embodiments of this specification also provide the solution that needs to be executed for registering the application server mentioned in FIG. 2 . The registered application server may be equipped with a back-end application, so that the back-end application can be used to process access requests sent by other devices. FIG. 3 is a schematic flowchart of a method for processing an access request provided by an embodiment of the present specification. As shown in FIG. 3 , the solution may include:

Step 302: the application server obtains the access request forwarded by the SLB server; the access request is that the SLB server queries the target corresponding to the target uniform resource locator according to the mapping table based on the access request containing the target uniform resource locator After the application server is the application server, the access request is forwarded to the application server; the target uniform resource locator at least includes a target domain name and a target path.

Step 304: The application server determines whether the access request is an access request supported by the application server based on the filtering rule pre-stored by the application server.

Step 306: If yes, process the access request.

Step 308: Otherwise, reject the access request.

In the embodiments of this specification, in order to improve the forwarding efficiency of access requests, the SLB server may use path regular expression verification or parameter existence verification to identify whether the application server supports processing access requests, and the accuracy of the identification results is higher than Low, therefore, there is a possibility that access requests not supported by the application server are erroneously forwarded to the application server.

In order to ensure the normal operation of the application server, before the application server processes the access request, the application server can also re-identify the access request according to the pre-stored filtering rules, so as to improve whether the application server supports processing the access request. The accuracy of the identification results can ensure the normal operation of the application server. After it is determined that the access request is supported, the application server processes it, and feeds back the processing result to the access request generator.

In the solution in FIG. 3, since the SLB server can identify in advance the access requests that some application servers do not support processing, and refuse to forward such access requests to the application server, the resource consumption of the application server in identifying the access requests can be reduced.

In this solution, the target URI in the access request can at least include the target domain name and the target path, and the supportable URI of the application server in the mapping table can also include at least the domain name and the path, so that the SLB server can The access request is accurately forwarded to further reduce the resource consumption of the application server in identifying the access request.

In this solution, by setting the supportable uniform resource locator of the application server according to the actual needs, the SLB server can forward the access requests of different domain names to the application server with the specified backend application for processing, so that the same Back-end applications support access requests from different front-end applications, which helps reduce the complexity and cost of application development and post-operation and maintenance.

In the embodiment of this specification, before the application server acquires the access request forwarded by the SLB server, it may further include:

The application server sends the supportable uniform resource locator of the application server to the SLB server, so that the SLB server associates the identifier of the application server with the supportable uniform resource locator of the application server and stores to the mapping table.

The application server sending the supportable uniform resource locator of the application server to the SLB server may specifically include:

The application server sends, to the SLB server, registration information including the application server's supportable uniform resource locator; or, in response to the SLB server's query request for the application server's supportable uniform resource locator , the application server sends the supportable uniform resource locator to the SLB server.

In the embodiment of this specification, the application server sends the implementation manner of the application server's supportable uniform resource locator to the SLB server, and the SLB server mentioned in the embodiment of the method in FIG. 2 obtains the application server's information from the application server. The implementation manner of the supportable uniform resource locator may be the same, which will not be repeated here.

Based on the same idea, the embodiments of the present specification also provide a device corresponding to the method in FIG. 2 . FIG. 4 is a schematic structural diagram of an access request forwarding apparatus corresponding to FIG. 2 according to an embodiment of the present specification. The apparatus in FIG. 4 can be applied to an SLB server. As shown in Figure 4, the apparatus may include:

The obtaining module 402 is configured to obtain an access request including a target uniform resource locator; the target uniform resource locator at least includes a target domain name and a target path.

The query module 404 is configured to query the target application server corresponding to the target uniform resource locator according to a mapping relationship table; the mapping relationship table is generated based on registration information of a registered application server, and the registration information includes the registered application A supportable uniform resource locator of the server; the supportable uniform resource locator includes at least a domain name and a path.

The forwarding module 406 is configured to forward the access request to the target application server.

Based on the device in FIG. 4 , some specific implementations of the device are also provided in the embodiments of the present specification, which will be described below.

Optionally, the apparatus in FIG. 4 may further include: an access denial module, configured to deny the access request if the target application server corresponding to the target uniform resource locator cannot be queried.

Optionally, the query module 404 may specifically include:

The first query unit is configured to query the initial target application server supporting the target domain name.

A second query unit, configured to query whether the path supported by the initial target application server includes the target path.

A determining unit, configured to determine the initial target application server as the target application server if the path supported by the initial target application server includes the target path.

Optionally, the query module 404 may further include:

an access denial unit, configured to reject the access request if an initial target application server supporting the target domain name is not found; or, if the path supported by the initial target application server does not contain the target path, reject the access request the access request.

Optionally, the query module 404 may be specifically configured to: query the target application server cluster corresponding to the target uniform resource locator.

The apparatus in FIG. 4 further includes: a determining module, which can be configured to determine a low-load target application server from the target application server cluster according to the real-time load indicators of each target application server in the target application server cluster; the low-load target application server; The real-time load index of the load target application server is smaller than the real-time load index of some target application servers in the target application server cluster.

The forwarding module 406 may be specifically configured to: forward the access request to the low-load target application server.

Optionally, the device in FIG. 4 may also include:

The registration information acquisition module is used to acquire the registration information of the registration application server.

An identification acquisition module, configured to acquire the identification of the registered application server.

The management storage module is configured to associate and store the identifier of the registered application server and the supportable uniform resource locator of the registered application server into the mapping relationship table.

Optionally, the device in FIG. 4 may also include:

An update information acquisition module, configured to acquire update information sent by the registered application server; the update information includes the updated supportable uniform resource locator of the registered application server.

An update module, configured to update the mapping relationship table according to the update information.

Optionally, the device in FIG. 4 may also include:

The interface information acquisition module is used for acquiring the interface information of the registered application server.

A supportable uniform resource locator query module is configured to query the supportable uniform resource locator of the registered application server through an interface corresponding to the interface information.

The associated storage module is configured to associate and store the identifier of the registered application server and the supportable uniform resource locator of the registered application server into the mapping relationship table.

Based on the same idea, the embodiment of the present specification also provides a device corresponding to the method in FIG. 3 . FIG. 5 is a schematic structural diagram of an apparatus for processing an access request corresponding to FIG. 3 according to an embodiment of the present specification. The apparatus in FIG. 3 may be applied to an application server. As shown in Figure 5, the apparatus may include:

The obtaining module 502 is configured to obtain the access request forwarded by the SLB server; the access request is that the SLB server queries the corresponding target uniform resource locator based on the access request including the target uniform resource locator according to the mapping table. After the target application server is the application server, the access request is forwarded to the application server; the target uniform resource locator at least includes a target domain name and a target path.

The judgment module 504 is configured to judge whether the access request is an access request supported by the application server based on the filtering rules pre-stored by the application server, and obtain a judgment result.

The access request processing module 506 is configured to process the access request when the judgment result indicates that the access request is an access request supported by the application server.

A denying access module 508 is configured to deny the access request when the judgment result indicates that the access request is not an access request supported by the application server.

Based on the device in FIG. 5 , the embodiments of this specification also provide some specific implementations of the device, which are described below.

Optionally, the device in FIG. 5 may also include:

A sending module, configured to send the supportable uniform resource locator of the application server to the SLB server, so that the SLB server associates the identifier of the application server with the supportable uniform resource locator of the application server stored in the mapping table.

Optionally, the sending module may be specifically configured to: send the registration information that includes the application server's supportable uniform resource locator to the SLB server; or,

The supportable uniform resource locator is sent to the SLB server in response to the SLB server's query request for the application server's supportable uniform resource locator.

Based on the same idea, the embodiments of this specification also provide an access request forwarding device corresponding to the method in FIG. 2 , and the access request forwarding device may be implemented by an SLB server. And, the embodiment of this specification also provides an access request processing device corresponding to the method in FIG. 3 , where the access request processing device may be an application server.

FIG. 6 is a schematic structural diagram of an access request forwarding device or an access request processing device according to an embodiment of the present specification.

As shown in FIG. 6, device 600 may include:

at least one processor 610; and,

a memory 630 in communication with the at least one processor; wherein,

The memory 630 stores instructions 620 executable by the at least one processor 610 .

When the device in FIG. 6 is an access request forwarding device corresponding to the method in FIG. 2 , the instructions 620 may be executed by the at least one processor 610, so that the at least one processor 610 can:

An access request containing a target uniform resource locator is obtained; the target uniform resource locator at least contains a target domain name and a target path.

According to the mapping relationship table, query the target application server corresponding to the target uniform resource locator; the mapping relationship table is generated based on the registration information of the registered application server, and the registration information includes the supportable uniform resources of the registered application server Locator; the supportable uniform resource locator contains at least a domain name and a path.

The access request is forwarded to the target application server.

When the device in FIG. 6 is an access request processing device corresponding to the method in FIG. 3 , the instructions 620 can be executed by the at least one processor 610, so that the at least one processor 610 can:

Obtain the access request forwarded by the SLB server; the access request is that the SLB server based on the access request containing the target uniform resource locator, according to the mapping relationship table, finds that the target application server corresponding to the target uniform resource locator is the After the device is installed, the access request is forwarded to the device; the target uniform resource locator at least includes a target domain name and a target path.

Based on the filtering rules pre-stored by the device, it is determined whether the access request is an access request supported by the device.

If so, process the access request. Otherwise, the access request is denied.

Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the forwarding device of the access request and the processing device of the access request, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts may refer to the partial descriptions of the method embodiments.

In the 1990s, improvements in a technology could be clearly differentiated between improvements in hardware (eg, improvements to circuit structures such as diodes, transistors, switches, etc.) or improvements in software (improvements in method flow). However, with the development of technology, the improvement of many methods and processes today can be regarded as a direct improvement of the hardware circuit structure. Designers almost get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by hardware entity modules. For example, a Programmable Logic Device (PLD) (eg, Field Programmable Gate Array (FPGA)) is an integrated circuit whose logic function is determined by user programming of the device. It is programmed by the designer to "integrate" a digital character system on a PLD, without the need for a chip manufacturer to design and manufacture a dedicated integrated circuit chip. And, instead of making integrated circuit chips by hand, these days, much of this programming is done using software called a "logic compiler", which is similar to the software compiler used in program development and writing, but before compiling The original code also has to be written in a specific programming language, which is called Hardware Description Language (HDL), and there is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language) , AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (RubyHardware Description Language), etc. The most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. It should also be clear to those skilled in the art that a hardware circuit for implementing the logic method process can be easily obtained by simply programming the method process in the above-mentioned several hardware description languages and programming it into the integrated circuit.

The controller may be implemented in any suitable manner, for example, the controller may take the form of eg a microprocessor or processor and a computer readable medium storing computer readable program code (eg software or firmware) executable by the (micro)processor , logic gates, switches, application specific integrated circuits (ASICs), programmable logic controllers and embedded microcontrollers, examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicon Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that, in addition to implementing the controller in the form of pure computer-readable program code, the controller can be implemented as logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded devices by logically programming the method steps. The same function can be realized in the form of a microcontroller, etc. Therefore, such a controller can be regarded as a hardware component, and the devices included therein for realizing various functions can also be regarded as a structure within the hardware component. Or even, the means for implementing various functions can be regarded as both a software module implementing a method and a structure within a hardware component.

The systems, devices, modules or units described in the above embodiments may be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device Or a combination of any of these devices.

For the convenience of description, when describing the above device, the functions are divided into various units and described respectively. Of course, when implementing the present application, the functions of each unit may be implemented in one or more software and/or hardware.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions The apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

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

Computer-readable media includes both persistent and non-permanent, removable and non-removable media, and storage of information may be implemented by any method or technology. Information may be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Flash Memory or other memory technology, Compact Disc Read Only Memory (CD-ROM), Digital Versatile Disc (DVD), or other optical storage , magnetic tape cartridges, magnetic tape-disk storage or other magnetic storage devices or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves.

It should also be noted that the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article or device comprising a series of elements includes not only those elements, but also Other elements not expressly listed, or which are inherent to such a process, method, article of manufacture, or apparatus are also included. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, article of manufacture, or device that includes the element.

It will be appreciated by those skilled in the art that the embodiments of the present application may be provided as a method, a system or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

The above descriptions are merely examples of the present application, and are not intended to limit the present application. Various modifications and variations of this application are possible for those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included within the scope of the claims of this application.

Claims (20)

1. A method for forwarding an access request based on an SLB server, comprising: The SLB server obtains an access request containing a target uniform resource locator; the target uniform resource locator at least contains a target domain name and a target path; According to the mapping relationship table, query the target application server corresponding to the target uniform resource locator; the mapping relationship table is generated based on the registration information of the registered application server, and the registration information includes the supportable uniform resources of the registered application server Locator; the supportable uniform resource locator at least includes a domain name and a path; The access request is forwarded to the target application server. 2. The method of claim 1, further comprising: If the target application server corresponding to the target uniform resource locator cannot be queried, the access request is rejected. 3. The method according to claim 1, wherein the querying the target application server corresponding to the target uniform resource locator specifically comprises: query the initial target application server supporting the target domain name; query whether the path supported by the initial target application server includes the target path; If the path supported by the initial target application server includes the target path, the initial target application server is determined as the target application server. 4. The method according to claim 3, after the querying an initial target application server supporting the target domain name, further comprising: If the initial target application server supporting the target domain name is not queried, the access request is rejected. 5. The method according to claim 3, after the querying whether the path supported by the initial target application server includes the target path, the method further comprises: If the path supported by the initial target application server does not contain the target path, the access request is rejected. 6. The method according to claim 1, wherein the querying the target application server corresponding to the target uniform resource locator specifically comprises: query the target application server cluster corresponding to the target uniform resource locator; Before forwarding the access request to the target application server, the method further includes: According to the real-time load index of each target application server in the target application server cluster, a low-load target application server is determined from the target application server cluster; the real-time load index of the low-load target application server is smaller than that of the target application server Real-time load indicators of some target application servers in the cluster; The forwarding of the access request to the target application server specifically includes: The access request is forwarded to the low-load target application server. 7. The method of claim 1, further comprising: obtaining the registration information of the registration application server; obtaining the identifier of the registered application server; The identifier of the registered application server and the supportable uniform resource locator of the registered application server are associated and stored in the mapping relationship table. 8. The method of claim 1, further comprising: acquiring update information sent by the registered application server; the update information includes the updated supportable uniform resource locator of the registered application server; According to the update information, the mapping relationship table is updated. 9. The method of claim 1, further comprising: Obtain the interface information of the registered application server; query the supported uniform resource locator of the registered application server through the interface corresponding to the interface information; The identifier of the registered application server and the supportable uniform resource locator of the registered application server are associated and stored in the mapping relationship table. 10. A method for processing an access request, comprising: The application server obtains the access request forwarded by the SLB server; the access request is that the SLB server based on the access request containing the target uniform resource locator, according to the mapping table, finds that the target application server corresponding to the target uniform resource locator is: After the application server, the access request is forwarded to the application server; the target uniform resource locator at least includes a target domain name and a target path; The application server determines whether the access request is an access request supported by the application server based on the filtering rule pre-stored by the application server; if so, process the access request; Otherwise, the access request is denied. 11. The method according to claim 10, before the application server obtains the access request forwarded by the SLB server, further comprising: The application server sends the supportable uniform resource locator of the application server to the SLB server, so that the SLB server associates the identifier of the application server with the supportable uniform resource locator of the application server and stores to the mapping table. 12. The method according to claim 11, wherein the application server sends the supportable uniform resource locator of the application server to the SLB server, specifically comprising: sending, by the application server to the SLB server, registration information including the application server's supportable uniform resource locator; or, In response to the query request of the SLB server for the supportable uniform resource locator of the application server, the application server sends the supportable uniform resource locator to the SLB server. 13. An access request forwarding device, applied to an SLB server, comprising: an obtaining module for obtaining an access request including a target uniform resource locator; the target uniform resource locator at least includes a target domain name and a target path; a query module, configured to query the target application server corresponding to the target uniform resource locator according to a mapping relationship table; the mapping relationship table is generated based on the registration information of the registration application server, and the registration information includes the registration application server The supportable uniform resource locator; the supportable uniform resource locator at least includes a domain name and a path; A forwarding module, configured to forward the access request to the target application server. 14. The device according to claim 13, wherein the query module specifically comprises: a first query unit, configured to query an initial target application server supporting the target domain name; a second query unit, configured to query whether the path supported by the initial target application server includes the target path; A determining unit, configured to determine the initial target application server as the target application server if the path supported by the initial target application server includes the target path. 15. The apparatus according to claim 14, the query module, further comprising: an access denial unit, configured to reject the access request if an initial target application server supporting the target domain name is not found; or, if the path supported by the initial target application server does not contain the target path, reject the access request the access request. 16. The device according to claim 13, wherein the query module is specifically used for: query the target application server cluster corresponding to the target uniform resource locator; The device further includes: a determining module configured to determine a low-load target application server from the target application server cluster according to the real-time load indicators of each target application server in the target application server cluster; the low-load target application server The real-time load index of the server is less than the real-time load index of some target application servers in the target application server cluster; The forwarding module is specifically used for: The access request is forwarded to the low-load target application server. 17. The apparatus of claim 13, further comprising: an interface information acquisition module, configured to acquire interface information of the registered application server; A supportable uniform resource locator query module, configured to query the supportable uniform resource locator of the registered application server through an interface corresponding to the interface information; The associated storage module is configured to associate and store the identifier of the registered application server and the supportable uniform resource locator of the registered application server into the mapping relationship table. 18. An apparatus for processing an access request, applied to an application server, comprising: The acquiring module is used to acquire the access request forwarded by the SLB server; the access request is that the SLB server queries the target corresponding to the target uniform resource locator based on the access request containing the target uniform resource locator according to the mapping table After the application server is the application server, it forwards the access request to the application server; the target uniform resource locator at least includes a target domain name and a target path; a judgment module, configured to judge whether the access request is an access request supported by the application server based on the filtering rules pre-stored by the application server, and obtain a judgment result; an access request processing module, configured to process the access request when the judgment result indicates that the access request is an access request supported by the application server; An access rejection module, configured to reject the access request when the judgment result indicates that the access request is not an access request supported by the application server. 19. An access request forwarding device, comprising: at least one processor; and, a memory communicatively coupled to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: Obtain an access request containing a target uniform resource locator; the target uniform resource locator at least contains a target domain name and a target path; According to the mapping relationship table, query the target application server corresponding to the target uniform resource locator; the mapping relationship table is generated based on the registration information of the registered application server, and the registration information includes the supportable uniform resources of the registered application server Locator; the supportable uniform resource locator at least includes a domain name and a path; The access request is forwarded to the target application server. 20. An access request processing device, comprising: at least one processor; and, a memory communicatively coupled to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: Obtain the access request forwarded by the SLB server; the access request is that the SLB server based on the access request containing the target uniform resource locator, according to the mapping relationship table, finds that the target application server corresponding to the target uniform resource locator is the After the device is installed, the access request is forwarded to the device; the target uniform resource locator at least includes the target domain name and the target path; Judging whether the access request is an access request supported by the device based on the filtering rules pre-stored by the device; if so, process the access request; Otherwise, the access request is denied.

Images