CN113761400A

CN113761400A - Access request forwarding method, device and equipment

Info

Publication number: CN113761400A
Application number: CN202010485002.XA
Authority: CN
Inventors: 韩喆
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2020-06-01
Filing date: 2020-06-01
Publication date: 2021-12-07

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

Access request forwarding method, device and equipment

Technical Field

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

Background

Currently, in the field of computer technology, the number of backend applications deployed on a server is increasing. After a plurality of access requests are forwarded to a server (hereinafter referred to as "application server") deployed with a backend application, the application server needs to identify the access requests forwarded to itself to determine whether the access requests are requests that can be processed by itself.

When the access requests reach a certain number, the occupation of resources of the application server is high by the process of identifying the access requests. In particular, with the rise of functions such as cloud-native functions, the consumption of processing resources of the application server by the functions such as cloud-native functions is also high.

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

Disclosure of Invention

The embodiment of the specification provides an access request forwarding method, an access request forwarding device and access request forwarding equipment, so that resource consumption of an application server in the aspect of identifying an access request is reduced.

In order to solve the above technical problem, the embodiments of the present specification are implemented as follows:

an access request forwarding method based on an SLB server provided in an embodiment of the present specification includes:

the SLB server acquires an access request containing a target uniform resource locator; the target uniform resource locator at least comprises a target domain name and a target path;

inquiring a target application server corresponding to the target uniform resource locator according to a mapping relation table; the mapping relation table is generated based on registration information of a registration application server, and the registration information comprises supportable uniform resource locators of the registration application server; the supportable uniform resource locator at least comprises a domain name and a path;

forwarding the access request to the target application server.

An access request processing method provided in an embodiment of the present specification includes:

the application server acquires an access request forwarded by the SLB server; the access request is transmitted to the application server after the SLB server inquires that a target application server corresponding to a target uniform resource locator is the application server according to a mapping relation table based on the access request containing the target uniform resource locator; the target uniform resource locator at least comprises a target domain name and a target path;

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

if so, processing the access request;

otherwise, the access request is denied.

An access request forwarding apparatus provided in an embodiment of the present specification is applied to an SLB server, and includes:

the acquisition module is used for acquiring an access request containing a target uniform resource locator; the target uniform resource locator at least comprises a target domain name and a target path;

the query module is used for querying a target application server corresponding to the target uniform resource locator according to the mapping relation table; the mapping relation table is generated based on registration information of a registration application server, and the registration information comprises supportable uniform resource locators of the registration application server; the supportable uniform resource locator at least comprises a domain name and a path;

and the forwarding module is used for forwarding the access request to the target application server.

An access request processing apparatus provided in an embodiment of the present specification, applied to an application server, includes:

the acquisition module is used for acquiring the access request forwarded by the SLB server; the access request is transmitted to the application server after the SLB server inquires that a target application server corresponding to a target uniform resource locator is the application server according to a mapping relation table based on the access request containing the target uniform resource locator; the target uniform resource locator at least comprises a target domain name and a target path;

the judging module is used for judging whether the access request is supported by the application server or not based on a filtering rule pre-stored by the application server to obtain a judging result;

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

and the access rejecting module is used for rejecting the access request when the judgment result shows that the access request is not the access request supported by the application server.

An access request forwarding device provided in an embodiment of the present specification includes:

at least one processor; and the number of the first and second groups,

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

the memory stores instructions executable by the at least one processor to enable the at least one processor to:

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

forwarding the access request to the target application server.

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

at least one processor; and the number of the first and second groups,

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

acquiring an access request forwarded by an SLB server; the access request is transmitted to the equipment after the SLB server inquires that a target application server corresponding to a target uniform resource locator is the equipment according to a mapping relation table based on the access request containing the target uniform resource locator; the target uniform resource locator at least comprises a target domain name and a target path;

judging whether the access request is an access request supported by the equipment or not based on a filter rule pre-stored by the equipment;

if so, processing the access request;

otherwise, the access request is denied.

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

the SLB server forwards the acquired access request containing the target uniform resource locator to a target application server supporting processing of the access request for processing according to a mapping relation table recorded with the mapping relation between the supportable uniform resource locator of the registered application server and the identifier of the registered application server, so that the target application server is not required to identify whether the target application server supports the processing of the access request, and the resource consumption of the application server in the aspect of identifying the access request is reduced.

In the scheme, the target uniform resource locator in the access request may at least include a target domain name and a target path, and the supportable uniform resource locator of the registered application server in the mapping relation table may also at least include a domain name and a path, so that the SLB server may accurately forward the access request, thereby further reducing resource consumption of the application server in identifying the access request.

Drawings

In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.

Fig. 1 is a schematic flowchart of an overall scheme of an access request forwarding method based on an SLB server in an embodiment of the present specification;

fig. 2 is a schematic flowchart of an access request forwarding method based on an SLB server according to an embodiment of the present disclosure;

fig. 3 is a flowchart illustrating a processing method of an access request according to an embodiment of the present disclosure;

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

fig. 5 is a schematic structural diagram of a processing device corresponding to an access request of fig. 3, provided in an embodiment of the present specification;

fig. 6 is a schematic structural diagram of an access request forwarding device corresponding to fig. 2 and a processing device corresponding to an access request of fig. 3, provided in an embodiment of this specification.

Detailed Description

To make the objects, technical solutions and advantages of one or more embodiments of the present disclosure more apparent, the technical solutions of one or more embodiments of the present disclosure will be described in detail and completely with reference to the specific embodiments of the present disclosure and the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present specification, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from the embodiments given herein without making any creative effort fall within the scope of protection of one or more embodiments of the present specification.

The technical solutions provided by the embodiments of the present description are 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 at a device such as a PC end, a mobile end, and the like, which can provide an application interface for a user to operate conveniently. The back-end application refers to an application program running at the application server corresponding to the front-end application, and the back-end application can interact with the database to process corresponding business logic and assist in realizing the functions of the front-end application.

Currently, when a server (hereinafter, referred to as an "application server") deployed with a back-end application receives an access request sent by a front-end application, it is generally necessary to identify whether the access request is a request that can be handled by itself. When the access requests reach a certain number, the occupation of resources of the application server is high by the process of identifying the access requests. Therefore, how to reduce the resource consumption of the application server in identifying the access request becomes a technical problem to be solved by those skilled in the art.

To facilitate understanding of the scheme in the embodiment, the SLB server is explained below.

A Server Load Balancing (SLB) Server refers to a Server that can distribute traffic to multiple servers in a Server cluster to balance the Load of devices in the Server cluster. In practical application, the SLB server may perform forwarding judgment and forwarding operation on the access request based on a 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 scheme of an access request forwarding method based on an SLB server in an embodiment of the present specification.

As shown in fig. 1, a first application is installed in the first registered application server 102, a second application is installed in the second registered application server 103, and both the first application and the second application may be backend applications. It is assumed that a first application in the first registered application server 102 supports the handling of access requests containing the uniform resource locator "http// a.cn/path 1" or "http// b.com/path 2", while a second application in the second registered application server 103 supports the handling of access requests containing the uniform resource locator

And c, d, c, g, c, g, c, f, h, g, h, c, n, p, g, c, n, p 3.

The first registered application server 102 and the second registered application server 103 may be registered in advance at the SLB server 101 so that the SLB server 101 generates the mapping relationship table. The mapping relationship table may record a 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 a mapping relationship between the identifier of the second registered application server 103 and the supportable uniform resource locator of the second registered application server 103. As an example, the mapping relationship recorded in the mapping relationship table generated by the SLB server 101 may include: mapping relation between ' 101 ' and ' http// a. cn/path1

Com/path2 "and between 102" and http// a.cn/path3 ".

Subsequently, when the SLB server 101 receives an access request, it may query, according to a mapping relationship table generated in advance, a registered application server capable of processing the access request in each server in the server cluster, and forward the access request to a corresponding registered application server for processing. For example, the first access request 104 and the second access request 105 are forwarded to the first registration application server 102 for processing, and the fourth access request 107 is forwarded to the second registration application server 103 for processing.

If the SLB server does not query a registered application server capable of processing the access request, the access request can be rejected without forwarding the access request. For example, if the first registered application server 102 and the second registered application server 103 do not support processing the third access request 106 according to the mapping relationship table, the SLB server may refuse to forward the third access request 106.

Next, an access request forwarding method based on an SLB server provided in an embodiment of the present disclosure is specifically described with reference to the accompanying drawings:

fig. 2 is a schematic flowchart of an access request forwarding method based on an SLB server according to an embodiment of the present disclosure. From the viewpoint of the program, the execution subject of the flow may be the SLB server or a program installed in the SLB server.

As shown in fig. 2, the process may include the following steps:

step 202: the SLB server acquires an access request containing a target uniform resource locator; the target uniform resource locator at least comprises a target domain name and a target path.

In the embodiments of the present disclosure, a Uniform Resource Locator (URL) may contain information such as a domain name and a path, and the uniform resource locator may be used to locate a specific resource. The Domain Name (Domain Name) may be a string of characters separated by dots, and the Domain Name may be used as a positioning identifier for the computer during data transmission. And a path may refer to a line that a file is being sought over. In practical applications, the path may include an absolute path and a relative path. For the sake of understanding, the target uniform resource locator is "http// a.cn/path 1", for example, the solution is described, wherein the domain name may be "a.cn". The absolute path may be "http// a. cn/path 1" and the relative path may be "path 1".

In this embodiment of the present disclosure, the access request carrying the target uniform resource locator may be various network requests carrying the target uniform resource locator, such as an http (hyper Text Transfer protocol) request, an ftp (file Transfer protocol) request, and the like. 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 this embodiment, the SLB server may distribute traffic to a plurality of servers in the server cluster, so as to implement load balancing among the servers in the server cluster. The server in the server cluster may be a server loaded with a backend application (i.e., an application server), and the application server may be configured to process an access request including a target uniform resource locator generated by a front-end application or another backend application. In practical applications, the server cluster may include one or more physical servers, or may include one or more virtual servers (e.g., cloud servers), which is not particularly limited.

In this embodiment of the present specification, when there is an access request including a target uniform resource locator, which is requested to be processed by a server cluster, the SLB server may obtain the access request, and determine whether to forward the access request to an application server in the server cluster for processing.

Step 204: inquiring a target application server corresponding to the target uniform resource locator according to a mapping relation table; the mapping relation table is generated based on registration information of a registration application server, and the registration information comprises supportable uniform resource locators of the registration application server; the supportable uniform resource locator includes at least a domain name and a path.

In this specification embodiment, the SLB server may forward the access request to the application server that completed registration at the SLB server (i.e., the registered application server). Therefore, the application server having the backend application installed therein needs to be registered in the SLB server in advance.

In this embodiment, the SLB server may obtain registration information of the registered application server, where the registration information may include uniform resource locators (i.e., supporting uniform resource locators) corresponding to resources that the registered application server may process. The SLB server can also generate a mapping relation table recorded with the mapping relation between the supportable uniform resource locator of the registered application server and the identification of the registered application server according to the registration information of the registered application server. Therefore, the SLB server can determine whether the access request acquired in step 202 is an access request that can be processed by the registered application server based on the mapping relationship table.

In this embodiment of the present specification, the supportable uniform resource locator in the registration information of the registration application server may be manually set according to actual situations. The supportable uniform resource locator of the registered application server may include one or more domain names and one or more paths.

For example, as shown in fig. 1, the supportable uniform resource locator of the first registered application server loaded with the first application includes "http// a.cn/path 1", "http// b.com/path 2", and the like. The supportable uniform resource locator of the second registered application server loaded with the second application may include

"http// a. cn/path 3", and the like. That is, both the first application and the second application can process the partial access request with the domain name "a.cn". And the first application may also support access to multiple domain names (e.g., "a.cn"),

Com ") of the access request.

In practical applications, since there are many applications that may only have a slight difference in front-end pages, but the back-end interface and the business logic may be the same, at present, two back-end applications with the same program code need to be deployed on a server to support different front-end applications respectively, and there is a problem that the deployment and maintenance costs of the back-end applications are high.

In this embodiment, the scheme in fig. 1 enables a user to set a supportable uniform resource locator of a registered application server according to actual needs, and enables an SLB server to forward an access request based on the supportable uniform resource locator of the registered application server, so that a backend application can be deployed on the server to support access requests with the same business logic sent by multiple front-end applications, for example, an access request for multiple domain names (e.g., "a.cn", "b.com") can be supported by a first application to be processed. The scheme is beneficial to reducing the complexity and cost of application development and later-stage operation and maintenance.

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

In this embodiment of the present specification, when the SLB server queries that there is an application server (i.e., a target application server) that can process an access request carrying the target uniform resource locator, the SLB server may forward the access request to the target application server, so that the target application server processes and responds to the access request.

In this embodiment of the present specification, when the target application server corresponding to the target uniform resource locator is not queried, it may indicate that none of the registered application servers at the SLB server supports processing of the access request, and therefore, the SLB server may reject the access request, and no longer forward the access request to the registered application server for identification of whether processing can be supported, so that resource consumption of the registered application server in identifying the access request may be reduced.

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

In the method in fig. 2, based on the principle that the SLB server can forward the access request to the registered application server to implement load balancing, the SLB server can forward the acquired access request including the target uniform resource locator to the target application server that supports processing the access request according to the mapping relationship table in which the mapping relationship between the supportable uniform resource locator of the registered application server and the identifier of the registered application server is recorded, so that it is not necessary for the target application server to identify whether or not it supports processing the access request, thereby reducing resource consumption of the application server in identifying the access request.

In the scheme, the SLB server can forward the access requests of different domain names to the registered application server loaded with the specified back-end application for processing, so that the access requests of different front-end applications can be supported by the same back-end application, and the complexity and the cost of application development and later operation and maintenance are reduced.

Based on the method of fig. 2, the embodiments of the present specification also provide some specific implementations of the method, which are described below.

In the present embodiment, step 204: querying a target application server corresponding to the target uniform resource locator may specifically include:

querying an initial target application server supporting the target domain name.

If the initial target application server supporting the target domain name is not inquired, rejecting the access request;

and if the initial target application server supporting the target domain name is inquired, inquiring whether the path supported by the initial target application server contains the target path.

And if the path supported by the initial target application server comprises the target path, determining the initial target application server as the target application server.

And if the path supported by the initial target application server does not contain the target path, rejecting the access request.

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

In this embodiment of the present specification, after rejecting the access request, the method may further include: and feeding back request failure information to the equipment sending the access request. So that the response latency of the device sending the access request to the access request can be reduced.

In the embodiment of the present specification, whether a registered application server supporting a target domain name in a target uniform resource locator exists is firstly queried, and if not, the query is stopped, and the access request is rejected.

In this embodiment, the SLB server may be used to implement load balancing of the server cluster. Thus, step 204: querying a target application server corresponding to the target uniform resource locator may specifically include: and querying a 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 application server from the target application server cluster according to the real-time load index of each target application server in the target application server cluster; and the real-time load index of the low-load target application server is smaller than the real-time load index of a part of target application servers in the target application server cluster.

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

In this embodiment, when the SLB server determines that there are a plurality of registered application servers (i.e., target application servers) that can support the access request acquired in processing step 202, the plurality of target application servers may be determined as servers in the target application server cluster.

The SLB server may determine a server with a lower current load from the target application server cluster as a low-load target application server, 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 embodiment of the present specification, the process of determining the low-load target application server by the SLB server is not particularly limited.

In practical application, because hardware resource configurations of different application servers are usually different, part of the application servers are more suitable for processing access requests which need to read and write high-frequency data, and part of the application servers are more suitable for processing access requests which have more requirements on GPU resources.

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 (API) of the registered Application server. In actual application, a user may specify a supportable interface of an application server in the registration information according to actual requirements, for example, the registration information of the application server with high IO efficiency includes an interface with high requirements for information input and output efficiency, such as transformAPI, and the transformAPI allows a third party plug-in to operate a compiled class file before the class file is converted into a dex file, so as to simplify the custom operation of the class file; the registration information of the application server with high GPU performance includes an interface with a large requirement on GPU resources or a high requirement on GPU operation efficiency, such as a compressed image API for compressing an image. Therefore, the SLB server can forward the access request with high IO to the registration application server with high IO efficiency for processing, and forward the access request with high GPU to the registration application server with high GPU performance for processing, and resource utilization rate of the registration application server and processing efficiency of the access request are improved.

In the embodiments of the present specification, there are various ways in which the SLB server generates the mapping relationship table.

In the first mode, when the application server registers at the SLB server:

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

And acquiring the identifier of the registered application server.

And storing the identifier of the registered application server and the supportable uniform resource locator of the registered application server in the mapping relation table in an associated manner.

In this implementation manner, the SLB server may transmit the supportable uniform resource locator of the registration application server based on the registration information of the registration application server, so that an additional step of transmitting the supportable uniform resource locator of the registration application server is not required, thereby reducing the modification of the SLB server and being beneficial to reducing the modification cost of the access request forwarding scheme.

In the second way, since the supportable uniform resource locator of the registered application server may be changed, in order to improve the accuracy of the SLB server for forwarding the access request, therefore,

the SLB server may be caused to acquire update information sent by the registered application server; the updated information includes an updated supportable uniform resource locator of the registered application server.

And updating the mapping relation table according to the updating information. For example, according to the updated information, the mapping relationship between the uniform resource locator no longer supported by the registered application server and the registered application server identifier in the mapping relationship table is deleted, or the mapping relationship between the newly added supportable uniform resource locator of the registered application server and the registered application server identifier is added in the mapping relationship table.

In the foregoing implementation manner, when the supportable 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 may also enable the SLB service to obtain the updated supportable uniform resource locator of the registered application server to update the mapping relationship table. Therefore, the operation stability and the forwarding accuracy of the access request forwarding scheme are improved.

In a third way, the registered application server can actively send the supported uniform resource locator to the SLB server. In addition, the SLB server may also actively request the registration application server for its supported uniform resource locators. Specifically, the method comprises the following steps:

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

And inquiring the supportable uniform resource locator of the registered application server through an interface corresponding to the interface information.

In this implementation manner, the registration application server may open an assigned interface to call the SLB server, so that the SLB server obtains the supportable uniform resource locator of the registration application server and the updated supportable uniform resource locator based on the interface, thereby maintaining the mapping relationship table, ensuring the real-time performance and accuracy of the mapping relationship table, and further reducing the probability of erroneous forwarding or erroneous rejection of the access request.

Based on the same idea, the embodiment of the present specification also provides a scheme that the registration application server mentioned in fig. 2 needs to execute. The registration application server may be loaded with a backend application, so that the backend application can be used to process access requests sent by other devices. Fig. 3 is a flowchart of a method for processing an access request according to an embodiment of the present disclosure, and as shown in fig. 3, the method may include:

step 302: the application server acquires an access request forwarded by the SLB server; the access request is transmitted to the application server after the SLB server inquires that a target application server corresponding to a target uniform resource locator is the application server according to a mapping relation table based on the access request containing the target uniform resource locator; the target uniform resource locator at least comprises a target domain name and a target path.

Step 304: and the application server judges whether the access request is supported by the application server or not based on a filtering rule pre-stored by the application server.

Step 306: if so, the access request is processed.

Step 308: otherwise, the access request is denied.

In this embodiment of the present specification, in order to improve the forwarding efficiency of the access request, the SLB server may use a path regular expression check or a parameter existence check to identify whether the application server supports processing of the access request, and the accuracy of the identification result is low, so that there is a possibility that the access request that is not supported by the application server is 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 perform secondary identification on the access request according to a pre-stored filtering rule, so as to improve the accuracy of an identification result of whether the application server supports processing the access request, thereby ensuring the normal operation of the application server. And after the access request is determined to be supported to be processed, the application server processes the access request and feeds back a processing result to the access request generator.

In the scheme in fig. 3, since the SLB server can recognize in advance that some application servers do not support the processed access request, and refuse to forward such access request to the application server, the resource consumption of the application server in recognizing the access request can be reduced.

In the scheme, the target uniform resource locator in the access request may at least include a target domain name and a target path, and the supportable uniform resource locator of the application server in the mapping relation table may also at least include a domain name and a path, so that the SLB server may accurately forward the access request, thereby further reducing resource consumption of the application server in identifying the access request.

In the scheme, the supportable uniform resource locator of the application server is set according to actual requirements, so that the SLB server can forward the access requests of different domain names to the application server loaded with the specified back-end application for processing, the access requests of different front-end applications can be supported by the same back-end application, and the reduction of complexity and cost of application development and later operation and maintenance is facilitated.

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

and the application server sends the supportable uniform resource locator of the application server to the SLB server, so that the SLB server stores the identifier of the application server and the supportable uniform resource locator of the application server in the mapping relation table in an associated manner.

Wherein, the sending, by the application server to the SLB server, a supportable uniform resource locator of the application server may specifically include:

the application server sends registration information containing supportable uniform resource locators of the application server to the SLB server; 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.

In this embodiment, the implementation manner in which the application server sends the supportable uniform resource locator of the application server to the SLB server may be the same as the implementation manner in which the SLB server obtains the supportable uniform resource locator of the application server from the application server, which is mentioned in the embodiment of the method in fig. 2, and is not described again.

Based on the same idea, the embodiment of the present specification further provides an apparatus corresponding to the method in fig. 2. Fig. 4 is a schematic structural diagram of an access request forwarding apparatus corresponding to fig. 2 provided in an embodiment of this specification. The apparatus in fig. 4 may be applied to an SLB server. As shown in fig. 4, the apparatus may include:

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

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

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

Based on the device of fig. 4, the present specification also provides some specific implementations of the device, which are described below.

Optionally, the apparatus in fig. 4 may further include: and the access refusing module is used for refusing the access request under the condition that the target application server corresponding to the target uniform resource locator is not inquired.

Optionally, the query module 404 may specifically include:

and the first query unit is used for querying an initial target application server supporting the target domain name.

And the second query unit is used for querying whether the path supported by the initial target application server contains 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:

the access rejection unit is used for rejecting the access request if the initial target application server supporting the target domain name is not inquired; or, the access request is rejected if the path supported by the initial target application server does not include the target path.

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

The apparatus in fig. 4 further comprises: the determining module may be configured to determine a low-load target application server from the target application server cluster according to a real-time load index of each target application server in the target application server cluster; and the real-time load index of the low-load target application server is smaller than the real-time load index of a part of target application servers in the target application server cluster.

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

Optionally, the apparatus in fig. 4 may further include:

and the registration information acquisition module is used for acquiring the registration information of the registration application server.

And the identification acquisition module is used for acquiring the identification of the registered application server.

And the management storage module is used for storing the identifier of the registered application server and the supportable uniform resource locator of the registered application server in a related manner to the mapping relation table.

Optionally, the apparatus in fig. 4 may further include:

the update information acquisition module is used for acquiring the update information sent by the registration application server; the updated information includes an updated supportable uniform resource locator of the registered application server.

And the updating module is used for updating the mapping relation table according to the updating information.

Optionally, the apparatus in fig. 4 may further include:

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

And the supportable uniform resource locator query module is used for querying the supportable uniform resource locator of the registered application server through the interface corresponding to the interface information.

And the association storage module is used for associating and storing the identifier of the registered application server and the supportable uniform resource locator of the registered application server to the mapping relation table.

Based on the same idea, the embodiment of the present specification further provides an apparatus corresponding to the method in fig. 3. Fig. 5 is a schematic structural diagram of a processing apparatus corresponding to an access request of fig. 3 according to an embodiment of the present disclosure, where the apparatus in fig. 3 may be applied to an application server. As shown in fig. 5, the apparatus may include:

an obtaining module 502, configured to obtain an access request forwarded by an SLB server; the access request is transmitted to the application server after the SLB server inquires that a target application server corresponding to a target uniform resource locator is the application server according to a mapping relation table based on the access request containing the target uniform resource locator; the target uniform resource locator at least comprises a target domain name and a target path.

A determining module 504, configured to determine, based on a filtering rule pre-stored by the application server, whether the access request is an access request supported by the application server, to obtain a determination result.

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

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

Based on the device of fig. 5, the present specification also provides some specific implementations of the device, which are described below.

Optionally, the apparatus in fig. 5 may further include:

a sending module, configured to send a supportable uniform resource locator of the application server to the SLB server, so that the SLB server stores the identifier of the application server and the supportable uniform resource locator of the application server in association with the mapping relationship table.

Optionally, the sending module may be specifically configured to: sending registration information containing a supportable uniform resource locator of the application server to the SLB server; or,

sending a supportable uniform resource locator to the SLB server in response to the SLB server's query request for the supportable uniform resource locator of the application server.

Based on the same idea, an embodiment of the present specification further provides an access request forwarding device corresponding to the method in fig. 2, where the access request forwarding device may be implemented by using an SLB server. And, the present 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 provided in an embodiment of this specification.

As shown in fig. 6, the apparatus 600 may include:

at least one processor 610; and the number of the first and second groups,

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

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

When the apparatus of fig. 6 is implemented as an access request forwarding apparatus corresponding to the method of fig. 2, the instructions 620 are executable by the at least one processor 610 to enable the at least one processor 610 to:

acquiring an access request containing a target uniform resource locator; the target uniform resource locator at least comprises a target domain name and a target path.

Inquiring a target application server corresponding to the target uniform resource locator according to a mapping relation table; the mapping relation table is generated based on registration information of a registration application server, and the registration information comprises supportable uniform resource locators of the registration application server; the supportable uniform resource locator includes at least a domain name and a path.

Forwarding the access request to the target application server.

When the apparatus of fig. 6 is implemented as an access request processing apparatus corresponding to the method of fig. 3, the instructions 620 are executable by the at least one processor 610 to enable the at least one processor 610 to:

acquiring an access request forwarded by an SLB server; the access request is transmitted to the equipment after the SLB server inquires that a target application server corresponding to a target uniform resource locator is the equipment according to a mapping relation table based on the access request containing the target uniform resource locator; the target uniform resource locator at least comprises a target domain name and a target path.

And judging whether the access request is an access request supported by the equipment or not based on a filter rule pre-stored by the equipment.

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

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. Especially, as for the forwarding device of the access request and the processing device of the access request, since they are basically similar to the method embodiment, the description is relatively simple, and for the relevant points, refer to the partial description of the method embodiment.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital character system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate a dedicated integrated circuit chip. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.

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

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

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium which can be used to store information which can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or 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, and the like) 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 memory storage devices.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. An access request forwarding method based on an SLB server comprises the following steps:

forwarding the access request to the target application server.

2. The method of claim 1, further comprising:

and if the target application server corresponding to the target uniform resource locator cannot be inquired, rejecting the access request.

3. The method according to claim 1, wherein the querying a target application server corresponding to the target uniform resource locator specifically includes:

querying an initial target application server supporting the target domain name;

inquiring whether the path supported by the initial target application server contains the target path;

4. The method of claim 3, after querying an initial target application server supporting the target domain name, further comprising:

and if the initial target application server supporting the target domain name is not inquired, rejecting the access request.

5. The method of claim 3, after said querying whether the path supported by the initial target application server includes the target path, further comprising:

6. The method according to claim 1, wherein the querying a target application server corresponding to the target uniform resource locator specifically includes:

querying a 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:

determining a low-load target application server from the target application server cluster according to the real-time load index of each target application server in the target application server cluster; the real-time load index of the low-load target application server is smaller than the real-time load index of a part of target application servers in the target application server cluster;

the forwarding the access request to the target application server specifically includes:

forwarding the access request to the low-load target application server.

7. The method of claim 1, further comprising:

acquiring registration information of the registration application server;

acquiring an identifier of the registered application server;

8. The method of claim 1, further comprising:

acquiring updating information sent by the registered application server; the updated information comprises a supportable uniform resource locator of the updated registered application server;

and updating the mapping relation table according to the updating information.

9. The method of claim 1, further comprising:

acquiring interface information of the registered application server;

inquiring a supportable uniform resource locator of the registered application server through an interface corresponding to the interface information;

10. A processing method of an access request comprises the following steps:

if so, processing the access request;

otherwise, the access request is denied.

11. The method of claim 10, wherein before the application server obtains the access request forwarded by the SLB server, the method further comprises:

12. The method of claim 11, wherein the sending, by the application server to the SLB server, a supportable uniform resource locator of the application server, specifically comprises:

the application server sends registration information containing supportable uniform resource locators of the application server to the SLB server;

or,

in response to the SLB server's query request for a 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 comprises:

14. The apparatus according to claim 13, wherein the query module specifically includes:

the first query unit is used for querying 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;

15. The apparatus of claim 14, the query module, further comprising:

16. The apparatus of claim 13, wherein the query module is specifically configured to:

the device further comprises: the determining module is used for determining a low-load target application server from the target application server cluster according to the real-time load index of each target application server in the target application server cluster; the real-time load index of the low-load target application server is smaller than the real-time load index of a part of target application servers in the target application server cluster;

the forwarding module is specifically configured to:

forwarding the access request to the low-load target application server.

17. The apparatus of claim 13, further comprising:

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

a supportable uniform resource locator query module, configured to query a supportable uniform resource locator of the registered application server through an interface corresponding to the interface information;

18. An access request processing device applied to an application server comprises:

19. An access request forwarding device comprising:

at least one processor; and the number of the first and second groups,

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

forwarding the access request to the target application server.

20. An apparatus for processing an access request, comprising:

at least one processor; and the number of the first and second groups,

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

if so, processing the access request;

otherwise, the access request is denied.