CN111147598A

CN111147598A - HTTP message processing method and device

Info

Publication number: CN111147598A
Application number: CN201911402783.5A
Authority: CN
Inventors: 周斌; 孙艳杰
Original assignee: Hangzhou DPTech Technologies Co Ltd
Current assignee: Hangzhou DPTech Technologies Co Ltd
Priority date: 2019-12-30
Filing date: 2019-12-30
Publication date: 2020-05-12
Anticipated expiration: 2039-12-30
Also published as: CN111147598B

Abstract

The embodiment of the application provides a method and a device for processing an HTTP message. In the method, load balancing equipment receives an HTTP message sent by client equipment; according to the header information of the HTTP message, determining a target matching rule matched with the header information from at least one configured HTTP message matching rule; and if the action item included in the target matching rule is the identifier of the designated server, forwarding the HTTP message to the designated server. The method and the device can realize load sharing of the service carried by the HTTP message.

Description

HTTP message processing method and device

Technical Field

The present application relates to the field of network communication technologies, and in particular, to a method and an apparatus for processing an HTTP message.

Background

The HyperText Transfer Protocol (HTTP) is an application layer Protocol, and performs information interaction based on a client/server (C/S) architecture.

In a server cluster composed of multiple servers, a load balancing device is often used to share HTTP messages sent by a client device to each server. The load balancing device generally shares load based on tuple information (e.g., source IP address) of the HTTP message, and shares the HTTP message with the same tuple information to the same server for processing.

If each server is deployed based on a service, for example, there is a server that processes a video service and a server that processes a voice service, the existing load sharing method cannot implement load sharing based on a service carried by an HTTP message.

Disclosure of Invention

In view of this, the present application provides a method and an apparatus for processing an HTTP message, so as to implement load sharing based on a service carried by the HTTP message.

In order to achieve the purpose of the application, the application provides the following technical scheme:

in a first aspect, the present application provides a method for processing an HTTP packet, where the method is applied to a load balancing device, and the method includes:

receiving an HTTP message sent by client equipment;

according to the header information of the HTTP message, determining a target matching rule matched with the header information from at least one configured HTTP message matching rule;

and if the action item included in the target matching rule is the identifier of the designated server, forwarding the HTTP message to the designated server.

Optionally, the method further includes:

and if the action item included in the target matching rule is the identifier of the specified page, pushing the specified page to the client equipment.

Optionally, the method further includes:

and if the action item included in the target matching rule is an identifier for indicating to close the connection, disconnecting the connection with the client equipment.

Optionally, the header of the HTTP message includes a plurality of header fields, and determining, according to the header information of the HTTP message, a target matching rule matching the header information from at least one configured HTTP message matching rule includes:

and executing the following matching operation aiming at each HTTP message matching rule:

acquiring a matching item included by an HTTP message matching rule, wherein the matching item includes an identifier of at least one target header field;

for each target header field, extracting a character string corresponding to the target header field from the HTTP message;

matching the character string corresponding to the target head field extracted from the HTTP message with at least one characteristic character string corresponding to the target head field in a characteristic library based on the matching condition corresponding to the target head field included in the HTTP message matching rule;

and if the matching of all target header fields is successful, determining that the current HTTP message matching rule is the target matching rule, and if not, returning to execute the matching operation aiming at the next HTTP message matching rule.

Optionally, the obtaining of the character string corresponding to the target header field includes:

and extracting a character string corresponding to the target header field from the header information by using an AC algorithm.

In a second aspect, the present application provides an HTTP packet processing apparatus, which is applied to a load balancing device, and the apparatus includes:

the receiving unit is used for receiving the HTTP message sent by the client equipment;

the determining unit is used for determining a target matching rule matched with the header information from at least one configured HTTP message matching rule according to the header information of the HTTP message;

and the sending unit is used for forwarding the HTTP message to the specified server if the action item included in the target matching rule is the identifier of the specified server.

Optionally, the apparatus further comprises:

and the pushing unit is used for pushing the specified page to the client equipment if the action item included in the target matching rule is the identifier of the specified page.

Optionally, the apparatus further comprises:

and the disconnection unit is used for disconnecting the connection with the client equipment if the action item included in the target matching rule is an identifier for indicating to close the connection.

Optionally, the header of the HTTP message includes a plurality of header fields, and the determining unit determines, according to the header information of the HTTP message, a target matching rule matching the header information from at least one configured HTTP message matching rule, where the determining unit includes:

Optionally, the obtaining, by the determining unit, the character string corresponding to the target header field includes:

As can be seen from the above description, in the present application, the load balancing device obtains header information of the HTTP message, where the header information includes information of a resource (service) requested by the client device. The load balancing equipment matches a preset HTTP message matching rule according to the header information, and shares the HTTP message to a specified server according to a server specified by the matched HTTP message matching rule, wherein the specified server is a server for processing the service requested by the client equipment, so that the load sharing of the service carried by the HTTP message is realized.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a flowchart illustrating an HTTP message processing method according to an embodiment of the present application;

FIG. 2 is a flow chart illustrating an implementation of determining a target matching rule according to an embodiment of the present disclosure;

fig. 3 is a schematic structural diagram of an HTTP message processing apparatus according to an embodiment of the present application;

fig. 4 is a schematic diagram of a hardware structure of a load balancing device according to an embodiment of the present application.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the embodiments of the present application. As used in the examples of this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in the embodiments of the present application to describe various information, the information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the negotiation information may also be referred to as second information, and similarly, the second information may also be referred to as negotiation information without departing from the scope of the embodiments of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

The embodiment of the application provides an HTTP message processing method. In the method, the load balancing equipment acquires the header information of the HTTP message, wherein the header information comprises the information of the service requested by the client equipment. And the load balancing equipment matches a preset HTTP message matching rule according to the header information and shares the HTTP message to the specified server according to the specified server in the matched HTTP message matching rule. Therefore, load sharing is carried out based on the service carried by the HTTP message.

In order to make the objects, technical solutions and advantages of the embodiments of the present application more clear, the embodiments of the present application are described in detail below with reference to the accompanying drawings and specific embodiments:

referring to fig. 1, a flowchart of an HTTP message processing method provided in the embodiment of the present application is shown. The flow is applied to the load balancing equipment.

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

step 101, a load balancing device receives an HTTP message sent by a client device.

The client device requests resources from the server by sending HTTP messages, i.e., requests the server to provide the required business services for it.

And the destination IP address of the HTTP message sent by the client equipment is a virtual IP address configured on the load balancing equipment. The virtual IP address is a shared IP address provided by a plurality of server pairs.

And after receiving the HTTP message sent by the client equipment, the load balancing equipment executes subsequent load sharing processing.

Step 102, the load balancing device determines a target matching rule matched with the header information from at least one configured HTTP message matching rule according to the header information of the HTTP message.

The load balancing equipment is pre-configured with at least one HTTP message matching rule, and the HTTP message matching rule is used for enabling the HTTP messages matched with the rule to share load based on services.

Specifically, after receiving the HTTP message sent by the client device in step 101, the load balancing device obtains header information of the HTTP message, where the header information includes related information of a service requested by the client device. And the load balancing equipment matches at least one preset HTTP message matching rule based on the header information.

If the header information does not hit any HTTP message matching rule, it indicates that the HTTP message does not need to be load-shared based on the service, and the HTTP message can be processed by adopting the existing load-sharing mode, or the HTTP message is distributed to a preset default server for processing.

If the header information hits a matching rule of an HTTP message, step 103 is performed. Here, the HTTP message matching rule on which the header information hits (matches) is referred to as a target matching rule.

Step 103, if the action item included in the target matching rule is the identifier of the designated server, the load balancing device forwards the HTTP packet to the designated server.

For the HTTP message matched to the target matching rule, corresponding operations need to be executed according to the action items included in the target matching rule.

Specifically, if the action item included in the target matching rule is the identifier of the designated server, which indicates that the designated server is responsible for providing the service of the service requested by the current client device, the load balancing device forwards the HTTP packet to the designated server for processing.

Thus, the flow shown in fig. 1 is completed.

As can be seen from the flow shown in fig. 1, in the embodiment of the present application, the load balancing device matches a preset HTTP message matching rule based on header information of an HTTP message, where the header information includes information of a service requested by a client device, and the HTTP message matching rule specifies a server that processes the service, so that load sharing based on a service carried by the HTTP message can be implemented.

As an embodiment, if the action item included in the target matching rule is an identifier of a specified page, the load balancing device obtains the specified page and pushes the specified page to the client device. As an example, when a server processing a certain service is maintaining, an action item of an HTTP message matching rule corresponding to the service may be configured as an identifier of a designated page, and the designated page prompts a user that the server is maintaining, so that after receiving an HTTP message matching the HTTP message matching rule, a load balancing device may push the designated page carrying the prompt information to the user based on the HTTP message matching rule, thereby bringing a good use experience to the user.

As an embodiment, if the action item included in the target matching rule is an identifier indicating to close the connection, the load balancing device disconnects the connection with the client device. Here, it should be noted that the client device establishes a TCP connection with the load balancing device through the virtual IP address configured on the load balancing device, and sends an HTTP message through the TCP connection.

As an example, when a server processing a certain service fails and cannot provide a service, an action item of an HTTP message matching rule corresponding to the service may be configured as an identifier indicating to close a connection, so that after receiving an HTTP message matching the HTTP message matching rule, a load balancing device disconnects a connection with a client device sending the HTTP message according to the action item of the HTTP message matching rule, so as to avoid occupying network resources.

It should be added that the action item of the target matching rule may include both the identifier of the specified page and the identifier of the closed connection. The load balancing device can push the specified page to the client device according to the identifier of the specified page, and prompt the current service state (such as server failure) to the user by using the specified page. And then, according to the identifier for closing the connection, disconnecting the connection with the client equipment. The purposes of prompting the user and saving network resources are achieved.

Next, a process of determining, by the load balancing device in step 102, a target matching rule matching the header information from at least one configured HTTP message matching rule according to the header information of the HTTP message is described. Referring to fig. 2, an implementation flow for determining a target matching rule is shown in the embodiment of the present application.

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

step 201, the load balancing device obtains the matching items included in the matching rule of the current HTTP message.

As previously described, the load balancing device is configured with at least one HTTP message matching rule. After the load balancing device receives the HTTP message through step 101, a target matching rule matching the header information of the current HTTP message needs to be determined from at least one HTTP message matching rule.

For this purpose, the load balancing device performs the following matching operation for each HTTP message matching rule: and acquiring a matching item included by the current HTTP message matching rule, wherein the matching item includes at least one identification of a header field of the HTTP message.

Here, the header information of the HTTP message includes a plurality of header fields (also referred to as header fields), such as a request method field, a Uniform Resource Identifier (URI) field, an HTTP version number field, a Host (Host) field, a Cookie field, and a custom field.

In this embodiment, the matching item of the HTTP message matching rule may include an identifier of the at least one header field. The identity of which header field or fields specifically contained needs to be configured according to the specific service. The header field included in the matching entry is referred to herein as a target header field.

Step 202, for each target header field, the load balancing device extracts a character string corresponding to the target header field from the HTTP message.

Here, the target header field is a field that needs to be matched in the HTTP message. Therefore, the load balancing equipment extracts the character string corresponding to the target header field from the HTTP message.

For one embodiment, the AC algorithm may be used to extract the character string corresponding to the target header field from the header information of the HTTP message. The AC algorithm is an efficient character string matching algorithm, and the character string corresponding to the target head field in the HTTP message can be extracted quickly and accurately by using the AC algorithm.

Step 203, the load balancing device matches the character string corresponding to the target header field extracted from the HTTP message with at least one feature character string corresponding to the target header field in the feature library based on the matching condition corresponding to the target header field included in the HTTP message matching rule.

Here, it should be noted that the HTTP message matching rule includes a matching condition corresponding to the target header field. For example, when the target header field is a request method field, the corresponding matching condition may be equal to; when the target header field is a URI field, the corresponding matching condition may be a containing, starting, ending, equal to, regular expression, file type; when the target header field is an HTTP version number field, the corresponding matching condition may be equal to; when the target header field is a Host field, the corresponding matching condition may be a regular expression including, starting from, ending at, equal to, etc.; when the target header field is a Cookie field, the corresponding matching condition may be a regular expression including, starting from, ending at, equal to, or the like; when the target header field is a custom field, its corresponding matching condition may be a containing, starting, ending, equal, regular expression.

In addition, it should be noted that each HTTP message matching rule corresponds to a feature library. The feature library is configured with feature character strings corresponding to all target header fields included in the HTTP message matching rules. The characteristic character string can be configured according to specific services provided by the server. Each target header field may correspond to a plurality of characteristic strings.

In this step, the load balancing device matches the character string corresponding to the target header field extracted from the HTTP message with the plurality of feature character strings corresponding to the target header field in the feature library based on the matching condition corresponding to the target header field. And if any characteristic character string is successfully matched, the target header field is considered to be successfully matched.

As an embodiment, the load balancing device may match a character string corresponding to a target header field extracted from the HTTP message with a plurality of feature character strings corresponding to the target header field in the feature library using an AC algorithm.

And step 204, if all the target header fields are successfully matched, determining that the current HTTP message matching rule is the target matching rule, and if not, returning to the step 201 to execute the matching operation aiming at the next HTTP message matching rule.

In this step, if all target header fields included in the current HTTP message matching rule are successfully matched, it is considered that the currently received HTTP message hits the HTTP message matching rule, and the load balancing device determines the HTTP message matching rule as a target matching rule and executes a corresponding operation according to an action item included in the target matching rule.

If the target header fields which are not successfully matched exist in the target header fields included in the current HTTP message matching rule, the received HTTP message is considered not to hit the current HTTP message matching rule, and step 201 is switched to match the next HTTP message matching rule.

Here, it should be noted that when a large number of HTTP message matching rules are configured in the load balancing device and a large number of feature strings are configured in the feature library of the HTTP message matching rules, the target matching rule search efficiency can be greatly improved by using the AC algorithm, thereby improving the efficiency of sharing the HTTP messages to the designated server.

Thus, the flow shown in fig. 2 is completed.

Through the process shown in fig. 2, the load balancing device may determine a target matching rule matched with the current HTTP message from the multiple HTTP message matching rules.

It should be added that, before performing step 102, the load balancing device may further obtain a source IP address of the HTTP message (an IP address of the client device), and determine whether the source IP address is located in a preset address object. Here, the address objects may be all addresses, IPv4 address objects, IPv6 address objects, or operator network segments (e.g., china mobile, china unicom, china telecom, china education network). When the preset address object is an IPv4 address object or an IPv6 address object, the preset address object may be specifically an IP address range of the client device that needs to perform load sharing based on the service. And when the source IP address of the HTTP message received by the load balancing device falls into the preset address object, performing the operations of step 102 and step 103.

The method provided by the embodiment of the present application is described above, and the apparatus provided by the embodiment of the present application is described below:

referring to fig. 3, a schematic structural diagram of an apparatus provided in an embodiment of the present application is shown. The device includes: a receiving unit 301, a determining unit 302 and a transmitting unit 303, wherein:

a receiving unit 301, configured to receive an HTTP message sent by a client device;

a determining unit 302, configured to determine, according to header information of the HTTP message, a target matching rule that matches the header information from at least one configured HTTP message matching rule;

a sending unit 303, configured to forward the HTTP packet to the specified server if the action item included in the target matching rule is an identifier of the specified server.

As an embodiment, the apparatus further comprises:

As an embodiment, the header of the HTTP message includes a plurality of header fields, and the determining unit 303 determines, according to the header information of the HTTP message, a target matching rule matching the header information from at least one configured HTTP message matching rule, including:

As an embodiment, the determining unit 302 obtains a character string corresponding to the target header field, including:

The description of the apparatus shown in fig. 3 is thus completed. In the embodiment of the application, the load balancing device matches a preset HTTP message matching rule based on header information of an HTTP message, the header information includes information of a service requested by the client device, and the HTTP message matching rule specifies a server for processing the service, so that load sharing based on the service carried by the HTTP message can be realized.

The following describes a load balancing device provided in an embodiment of the present application:

referring to fig. 4, a hardware structure diagram of a load balancing device provided in the embodiment of the present application is shown. The load balancing device may include a processor 401, a machine-readable storage medium 402 having stored thereon machine-executable instructions. The processor 401 and the machine-readable storage medium 402 may communicate via a system bus 403. Also, the processor 401 may perform the HTTP message processing method described above by reading and executing machine-executable instructions in the machine-readable storage medium 402 corresponding to the HTTP message processing logic.

The machine-readable storage medium 402 referred to herein may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the machine-readable storage medium 402 may include at least one of the following storage media: volatile memory, non-volatile memory, other types of storage media. The volatile Memory may be a Random Access Memory (RAM), and the nonvolatile Memory may be a flash Memory, a storage drive (e.g., a hard disk drive), a solid state disk, and a storage disk (e.g., a compact disk, a DVD).

Embodiments of the present application also provide a machine-readable storage medium, such as the machine-readable storage medium 402 in fig. 4, including machine-executable instructions, which can be executed by the processor 401 in the load balancing device to implement the HTTP message processing method described above.

So far, the description of the apparatus shown in fig. 4 is completed.

The above description is only a preferred embodiment of the present application, and should not be taken as limiting the present application, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present application shall be included in the scope of the present application.

Claims

1. A method for processing Hyper Text Transfer Protocol (HTTP) messages is applied to load balancing equipment, and the method comprises the following steps:

receiving an HTTP message sent by client equipment;

2. The method of claim 1, wherein the method further comprises:

3. The method of claim 1, wherein the method further comprises:

4. The method according to any one of claims 1 to 3, wherein the header of the HTTP message comprises a plurality of header fields, and the determining, according to the header information of the HTTP message, a target matching rule matching the header information from at least one configured HTTP message matching rule comprises:

5. The method of claim 4, wherein the obtaining the string corresponding to the target header field comprises:

6. A Hyper Text Transfer Protocol (HTTP) message processing device is applied to load balancing equipment, and the device comprises:

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

8. The apparatus of claim 6, wherein the apparatus further comprises:

9. The apparatus according to any one of claims 6 to 8, wherein the header of the HTTP message includes a plurality of header fields, and the determining unit determines, from the configured at least one HTTP message matching rule, a target matching rule matching the header information according to the header information of the HTTP message, including:

10. The apparatus as claimed in claim 9, wherein said determining unit obtains the character string corresponding to the target header field, comprising: