CN110233902B

CN110233902B - Session processing method and device, electronic equipment and machine-readable storage medium

Info

Publication number: CN110233902B
Application number: CN201910577047.7A
Authority: CN
Inventors: 湛剑; 孙艳杰
Original assignee: Hangzhou DPTech Technologies Co Ltd
Current assignee: Hangzhou DPTech Technologies Co Ltd
Priority date: 2019-06-28
Filing date: 2019-06-28
Publication date: 2022-03-01
Anticipated expiration: 2039-06-28
Also published as: CN110233902A

Abstract

The application provides a session processing method, a session processing device, an electronic device and a machine-readable storage medium. In the application, a first session request carrying an inserted cookie of the client is received; creating a source IP session holding table entry corresponding to the inserted cookie of the first session request; and if a second session request which does not carry the inserted cookie and is received from the client is received, executing corresponding session processing of source IP session maintenance on the second session request based on the source IP session maintenance table entry. Based on the association of the cookie and the source IP session holding list item, the session request corresponding to the cookie is forwarded to the last accessed server through the associated source IP session holding list item after the cookie is lost, so that the session interruption is prevented, and the service continuity is ensured.

Description

Session processing method and device, electronic equipment and machine-readable storage medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a session processing method and apparatus, an electronic device, and a machine-readable storage medium.

Background

cookies, also known as cookies, are a technique that enables a Web server to store small amounts of data to or read data from the hard disk of a client (host computer where the browser resides).

When the method is implemented, when a user browses a website provided by a Web server through a browser, the Web server can record information such as user ID, password, browsed webpage, staying time and the like of the website through a very small text file arranged on a hard disk of a client side where the browser is located. When the user accesses the website again, the Web server reads the cookie to obtain the relevant information of the user, and then can make corresponding actions, such as displaying a slogan welcoming the user on a page, or allowing the user to directly log in without inputting an ID and a password, and the like. Essentially, a cookie can be considered as an identification card for a user. But cookies cannot be executed as code, do not transmit viruses, are proprietary to the user, and can only be read by the Web server that provides it. Most of the contents in the cookie are encrypted, so that the general user only looks like certain meaningless alphanumeric combinations, and only the Web processing program of the Web server knows the true meanings of the combinations.

Disclosure of Invention

The application provides a session processing method, which is applied to load balancing equipment in a load balancing system, wherein the load balancing system further comprises a client and a server; the client is connected with the server for communication through the load balancing equipment, and the method comprises the following steps:

receiving a first session request carrying an inserted cookie of the client;

creating a source IP session holding table entry corresponding to the inserted cookie of the first session request;

and if a second session request which does not carry the inserted cookie and is received from the client is received, executing corresponding session processing of source IP session maintenance on the second session request based on the source IP session maintenance table entry.

Optionally, the source IP session holding entry at least includes an IP address of a server corresponding to the client, and the performing, based on the source IP session holding entry, session processing of corresponding source IP session holding on the second session request includes:

and forwarding the second session request to an IP address of a server corresponding to the client.

Optionally, the method further includes:

updating the aging time of the source IP conversation maintaining table item according to a preset strategy; wherein the aging time is greater than an expiration time of the inserted cookie.

Optionally, the method further includes:

and if a third session request carrying the inserted cookie is received from the client, forwarding the third session request to the IP address of the server corresponding to the inserted cookie.

The application also provides a session processing device, which is applied to load balancing equipment in a load balancing system, wherein the load balancing system further comprises a client and a server; wherein, the client is connected with the server through the load balancing device for communication, and the device comprises:

the receiving module is used for receiving a first session request carrying an inserted cookie of the client;

a creating module for creating a source IP session holding table entry corresponding to the inserted cookie of the first session request;

and the session processing module is used for executing corresponding session processing of source IP session maintenance on the second session request based on the source IP session maintenance table entry if the second session request which does not carry the inserted cookie is received from the client.

Optionally, the source IP session holding table entry at least includes an IP address of a server corresponding to the client, and the session processing module further:

Optionally, the session processing module further:

The application also provides an electronic device, which comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are mutually connected through the bus;

the memory stores machine-readable instructions, and the processor executes the method by calling the machine-readable instructions.

The present application also provides a machine-readable storage medium having stored thereon machine-readable instructions which, when invoked and executed by a processor, implement the above-described method.

Through the embodiment, based on the association of the cookie and the source IP session holding table entry, the session request corresponding to the cookie is forwarded to the last accessed server through the associated source IP session holding table entry after the cookie is lost, so that session interruption is prevented, and the service continuity is ensured.

Drawings

FIG. 1 is a networking diagram of a load balancing system provided by an exemplary embodiment;

FIG. 2 is a flow diagram of a method for session processing in accordance with an illustrative embodiment;

FIG. 3 is a block diagram of a session processing apparatus provided in an exemplary embodiment;

fig. 4 is a hardware block diagram of an electronic device according to an exemplary embodiment.

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 herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in 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 is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope 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.

In order to make those skilled in the art better understand the technical solution in the embodiment of the present application, the following briefly describes the related art of session processing related to the embodiment of the present application.

Referring to fig. 1, fig. 1 is a networking diagram of a load balancing system according to an embodiment of the present application.

The load balancing system shown in fig. 1 includes: load balancing equipment (SLB), clients (C1, C2, C3), servers (S1, S2, S3);

the client is connected with the server for communication through the load balancing device via the network shown in fig. 1.

In implementation, a session request from a client to a server as shown in fig. 1 may be forwarded to the server selected by the load balancing algorithm through the load balancing device.

For example: the SLB may forward the session request from the C1 client to the server through load balancing S1; the SLB may forward the session request from the C2 client to the server through load balancing S2; the SLB may forward session requests from the C3 client to the server S3 through load balancing.

On the basis of the networking architecture shown above, the present application aims to propose a technical solution of session processing based on the association of a cookie with a source IP session holding entry.

When the method is realized, the load balancing system comprises load balancing equipment, a client and a server; and the client is connected with the server for communication through the load balancing equipment.

Further, the load balancing equipment receives a first session request carrying an inserted cookie of the client; creating a source IP session holding table entry corresponding to the inserted cookie of the first session request; and if a second session request which does not carry the inserted cookie and is received from the client is received, executing corresponding session processing of source IP session maintenance on the second session request based on the source IP session maintenance table entry.

In the above scheme, based on the association of the cookie and the source IP session holding entry, the session request corresponding to the cookie is forwarded to the last accessed server through the associated source IP session holding entry after the cookie is lost, so that session interruption is prevented, and service continuity is ensured.

The present application is described below with reference to specific embodiments and specific application scenarios.

Referring to fig. 2, fig. 2 is a flowchart of a session processing method according to an embodiment of the present application, where the method is applied to a load balancing device in a load balancing system, where the load balancing system further includes a client and a server; the client is connected with the server through the load balancing equipment for communication, and the method comprises the following steps:

step 202, receiving a first session request carrying an inserted cookie from the client.

Step 204, creating a source IP session holding table entry corresponding to the inserted cookie of the first session request.

Step 206, if a second session request carrying no cookie is received from the client, executing a corresponding session process of source IP session maintenance on the second session request based on the source IP session maintenance entry.

In this specification, the load balancing device may include any device integrated with a load balancing function. For example, in practical applications, the load balancing device may specifically include a switch, a router, a firewall, a server, a load balancer, and the like, which have a load balancing function.

In this specification, the client includes one or more devices that initiate a session request to the server.

For example, the client may include one or more of C1, C2, and C3 as shown in fig. 1.

In this specification, the server includes one or more devices that receive the session initiation request from the client and execute corresponding service processing.

For example, the server may include one or a combination of S1, S2, and S3 shown in fig. 1.

In this specification, the session request refers to a http (HyperText Transfer Protocol) or https (HyperText Transfer Protocol over Secure Socket Layer) service request message that is initiated by the client to the server.

For example, as shown in fig. 1, the session request may be an http-based service request message initiated from C1 to S1, or may be an https-based service request message initiated from C1 to S1.

In this specification, the load balancing system refers to an entire network system including the load balancing device, the client, and the server; and the client is connected with the server for communication through the load balancing equipment.

For example: referring to fig. 1, the load balancing system includes an SLB (the load balancing device), the client (C1, C2, C3), and the server (S1, S2, S3); and the client is connected with the server for communication through the load balancing equipment.

The following describes the technical solution related to the present application in detail by specific embodiments and in combination with "creation of cookie associated entries", "processing of a cookie lost session", and "processing of a cookie not lost session":

in this specification, the client initiates a session request to the server; the session request is forwarded to the server through the load balancing device and a preset load balancing algorithm, so that the server executes corresponding service processing for the session request.

When the method is implemented, the load balancing equipment provides the virtual service address for the client. The client may send a session request by accessing the virtual service address, and the load balancing device may distribute the session request to the server through the virtual service address.

For example, referring to fig. 1, the virtual service address of the SLB shown in fig. 1 is 100.30.5.1, and the load balancing device SLB provides a virtual service address 100.30.5.1 to the client (C1, C2, C3). The client may send a session request by accessing the virtual service address, and the load balancing device SLB may distribute the session request to the server through the virtual service address.

It should be noted that the session request from the client to the server may have various corresponding combinations, such as: C1-S1, C2-S2, C3-S3; for another example: the correspondence relationship between the clients and the session requests of the servers is not specifically limited in this description, and the clients and the servers are C1-S2, C2-S3, and C3-S1.

In this specification, after receiving the session request from the client, the server further executes service processing corresponding to the session request, and returns a session response corresponding to the session request to the client through the load balancing device.

For example, as shown in fig. 1, the client is S1, the client is C1, and S1 further executes service processing corresponding to the session request after receiving the session request of C1, and returns a session response corresponding to the session request to C1 through the load balancing device SLB.

In this specification, the inserting a cookie refers to a cookie in which the load balancing device inserts the server information of the server into a specified position in the header of the session response after receiving the session response of the server.

Continuing the example from the above example, after the load balancing device SLB receives the session response corresponding to the session request of C1 from S1, the load balancing device SLB inserts the server information of S1 (such as the IP address of S1, the server type of S1, etc.) in the form of cookie into the header specified location of the session response.

In this specification, further, after the insertion cookie is inserted into the session response, the load balancing apparatus sends the session response to the client.

Continuing with the above example, the load balancing device sends an inserted cookie carrying the server information of S1 to C1.

In this specification, the client may further acquire the inserted cookie from the load balancing device and store the inserted cookie locally, so that when the client initiates a next session request, the client may carry the inserted cookie and the load balancing device may analyze the inserted cookie in the session request to obtain server information corresponding to a previous session request in the inserted cookie, where the server information includes: the IP address of S1 so that the next session request is forwarded by the load balancing device to S1.

In this specification, the first session request refers to the session request carrying the inserted cookie from the client.

Continuing the example from the above example, the first session request may be the session request of C1 carrying the inserted cookie (the inserted cookie carrying the server information of S1).

In this specification, the load balancing device receives the first session request carrying the inserted cookie from the client.

Continuing the example from the above example, the SLB receives the session request of C1 carrying the above-mentioned insert cookie (the insert cookie carrying the server information of S1).

For ease of understanding, the following "source IP session maintenance" concept is introduced here first. In general, when load balancing is performed by the load balancing device, the source IP address of the access request is used as a main basis for allocating a corresponding server; the term "source IP session maintenance" refers to that the load balancing device distributes all access requests of a client to the same server when load balancing all access requests of the client from the same source IP address.

When the method is realized, the load balancing equipment executes the session processing of the source IP session maintenance based on the source IP session maintenance table; the source IP session holding table at least comprises a source IP address corresponding to the session request and a server IP address correspondingly allocated to the session request.

Continuing the example from the above example, the table structure and entry contents of the source IP session holding table are shown in table 1:

TABLE 1

Each row shown in table 1 corresponds to a source IP session holding entry in the "source IP session holding table". When load balancing is performed on the target session request with the corresponding client device C1 from the same source IP address of 10.30.5.6, the load balancing device allocates all access requests of the client device C1 to the corresponding server device S1 with the IP address of 100.30.5.6. Similarly, as shown in table 1, C2 and S2, C3 and S3 correspond to the respective source IP session holding entries.

In this specification, the source IP session holding table entry refers to a corresponding table entry in a "source IP session holding table" that is established by the load balancing device for the client and the corresponding server; the source IP session holding table entry at least includes an IP address of a server corresponding to the client.

Continuing the example from the above example, if the client is C1, the source IP session holding entry corresponding to C1 is shown in the first row of table 1, and the IP address of the server corresponding to the source IP session holding entry is 100.30.5.6 (the IP address of S1 shown in fig. 1).

Of course, in implementation, the source IP session holding table entry further includes the source IP address of the client (see the "source IP address" field shown in table 1).

In this specification, after receiving the first session request, the load balancing device creates a source IP session holding entry corresponding to the inserted cookie of the first session request.

Continuing the example from the above example, the load balancing device SLB creates a source IP session holding entry corresponding to the insert cookie (the insert cookie carrying the server information of S1) of the first session request (C1), and a source IP session holding table associated with the insert cookie, please refer to the example in table 2:

TABLE 2

The source IP session holding table shown in table 2 is modified from table 1, and table 2 is different from table 1 in that table 2 is added with an "association insert cookie" field compared to table 1, and after the field is added, each source IP session holding table entry (corresponding to one row in table 2) can associate the "source IP session holding table entry" shown in table 1 with the "insert cookie", that is, the source IP session holding table entry also stores the corresponding relationship with the insert cookie requested by the first session on the basis of the original table entry of the "source IP session holding table".

In the conventional implementation, the load balancing method based on the "source IP session holding table" and the load balancing method based on the "cookie insertion" are independent and unrelated to each other. While

In this specification, the second session request refers to the session request that does not carry the inserted cookie, of the client after the first session request.

Continuing the example from the above example, when cookie information is manually cleared (user security is guaranteed), or the life cycle of the cookie reaches a time limit, or after the cookie is automatically cleared by the system after the user closes the browser, the client sends the session request without the cookie, such as: the second session request may be the session request of C1 after the first request, which does not carry the inserted cookie (which does not carry the server information of S1).

In this specification, after the client sends the second session request, the load balancing device, upon receiving the second session request from the client, performs a session process of holding a corresponding source IP session for the second session request based on the source IP session holding entry.

Continuing the example from the above example, if the load balancing apparatus SLB receives the second session request of C1, the load balancing apparatus SLB performs the session process of the corresponding source IP session holding on the second session request based on the corresponding source IP session holding entry as shown in table 2.

In an illustrated embodiment, the load balancing device forwards the second session request to an IP address of a server corresponding to the client.

Continuing the example from the above example, the load balancing apparatus SLB forwards the above second session request of C1 to the IP address 100.30.5.6 of the server S1 corresponding to C1.

For convenience of understanding, the "aging time" is introduced here first, and since the resource of the load balancing device is limited, the number of source IP session holding entries in the source IP session holding table is also limited, and generally, the load balancing device sets the aging time corresponding to the source IP session holding entries to delete the source IP session holding entries corresponding to sessions without message interaction after the source IP session holding entries exceed the preset aging time (i.e., aging period). Such as: the aging time is 5 minutes, and within 5 minutes, if there is no message interaction in 3 sessions corresponding to 3 source IP session holding entries shown in table 2, the load balancing device deletes the 3 source IP session holding entries after 5 minutes.

In this specification, the expiration time of the inserted cookie is a life cycle of the inserted cookie.

In implementation, a cookie is inserted as a cookie by which there is a life cycle. The cookie lifetime, i.e. the expiration time of the cookie, is usually indicated by the value of the expire field in the cookie, and the cookie is valid during the lifetime and is automatically deleted beyond the lifetime; when the value of Exprire is 0 or null, it indicates that no cookie is saved when the user exits the browser (located on the client) to ensure the information security of the user. For example, the expiration time of the cookie insertion may be more than 10 minutes, more than 2 hours, more than 2 days, more than 1 month, or the like.

In this specification, after forwarding the second session request to the IP address of the server corresponding to the client, the load balancing device needs to update the aging time of the source IP session holding entry.

In an embodiment shown in the foregoing description, the load balancing device updates the aging time of the source IP session holding entry according to a preset policy; wherein the aging time is greater than the expiration time of the inserted cookie.

Continuing the example from the above example, assuming that the expiration time of the above inserted cookie is T (any length of time), the aging time of the IP session holding entry is greater than the aging time according to a preset policy, such as: the aging time of the IP session maintaining table entry is 2T + 1. After the load balancing device SLB forwards the second session request of C1 to the IP address 100.30.5.6 of the server S1 corresponding to C1, the load balancing device SLB updates the aging time of the IP session holding entry (the first row shown in table 2) corresponding to the session to 2T +1 according to the preset policy.

In this specification, the third session request refers to the session request carrying the inserted cookie of the client after the first session request.

Continuing the example from the above example, the third session request may be the session request carrying the insert cookie (the insert cookie carrying the server information of S1) of C1 after the first session request. The third session request may be the session request carrying the insert cookie (the insert cookie carrying the server information of S2) of C1 subsequent to the first session request.

In this specification, after receiving the third session request, the load balancing device may perform forwarding on the third session request based on an inserted cookie in the third session request.

In an embodiment shown in the present invention, if the load balancing device receives the third session request carrying an inserted cookie from the client, the load balancing device forwards the third session request to an IP address of a server corresponding to the inserted cookie.

Continuing to take an example from the above example, after receiving the third session request, the load balancing device may forward the third session request to the IP address of the server corresponding to the inserted cookie carried by the third session request. Such as: if the inserted cookie corresponding to the third session request carries server information of S1, the load balancing device SLB may forward the third session request to S1 shown in fig. 1; if the inserted cookie corresponding to the third session request carries server information of S2, the load balancing device SLB may forward the third session request to S2 shown in fig. 1.

In the technical scheme, based on the association of the cookie and the source IP session holding table entry, on one hand, after the cookie is lost, the session request corresponding to the cookie is forwarded to the last accessed server through the associated source IP session holding table entry, so that the session interruption is prevented, and the service continuity is ensured; on the other hand, the load balancing device can simultaneously support the forwarding of the session request based on the cookie and the session maintenance based on the source IP session, and overcomes the defect that the existing scheme can only support the forwarding of the session request based on the cookie session or the session request based on the session maintenance of the source IP session.

Fig. 3 is a block diagram of a session processing apparatus according to an exemplary embodiment of the present application. Corresponding to the embodiment of the method, the application also provides an embodiment of a session processing device, the device is applied to load balancing equipment in a load balancing system, and the load balancing system further comprises a client and a server; the client connects to the server via the load balancing device for communication, please refer to a session processing apparatus 30 illustrated in fig. 3, which includes:

a receiving module 301, configured to receive a first session request carrying an inserted cookie from the client;

a creating module 302 for creating a source IP session holding entry corresponding to the inserted cookie of the first session request;

if a second session request carrying no inserted cookie is received from the client, the session processing module 303 executes session processing of corresponding source IP session holding on the second session request based on the source IP session holding entry.

In this embodiment, the source IP session holding entry at least includes an IP address of a server corresponding to the client, and the session processing module 303 further:

In this embodiment, the session processing module 303 further:

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, wherein the modules described as separate parts may or may not be physically separate, and the parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.

The systems, devices, modules or modules illustrated in the above embodiments may be implemented by a computer chip or an entity, or by an article of manufacture with certain functionality. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

The embodiment of the session processing apparatus of the present application can be applied to the electronic device shown in fig. 4. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a logical device, the device is a machine executable instruction formed by reading a corresponding computer program instruction in a machine readable storage medium through a processor of the electronic device where the device is located and then running the computer program instruction. From a hardware aspect, as shown in fig. 4, the present application is a hardware structure diagram of an electronic device where a session processing apparatus is located, and except for the processor, the communication interface, the bus, and the machine-readable storage medium shown in fig. 4, the electronic device where the apparatus is located in the embodiment may also include other hardware according to an actual function of the electronic device, which is not described again.

Correspondingly, an embodiment of the present application further provides a hardware structure of an electronic device of the apparatus shown in fig. 3, please refer to fig. 4, and fig. 4 is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. The apparatus comprises: a communication interface 401, a processor 402, a machine-readable storage medium 403, and a bus 404; the communication interface 401, the processor 402 and the machine-readable storage medium 403 are configured to communicate with each other via a bus 404. The communication interface 401 is used for performing network communication. The processor 402 may be a Central Processing Unit (CPU), and the processor 402 may execute machine-readable instructions stored in a machine-readable storage medium 403 to implement the methods described above.

The machine-readable storage medium 403 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 may be: volatile memory, non-volatile memory, or similar storage media. In particular, the machine-readable storage medium 403 may be a RAM (random Access Memory), a flash Memory, a storage drive (e.g., a hard disk drive), a solid state disk, any type of storage disk (e.g., a compact disk, a DVD, etc.), or similar storage medium, or a combination thereof.

Up to this point, the description of the hardware configuration shown in fig. 4 is completed.

Furthermore, the present application also provides a machine-readable storage medium, such as the machine-readable storage medium 403 in fig. 4, including machine-executable instructions, which can be executed by the processor 402 in the session processing apparatus to implement the data processing method described above.

The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims

1. A conversation processing method is characterized in that the method is applied to load balancing equipment in a load balancing system, and the load balancing system further comprises a client and a server; the client is connected with the server for communication through the load balancing equipment, and the method comprises the following steps:

receiving a first session request carrying an inserted cookie of the client;

creating a source IP session holding entry corresponding to an insert cookie of the first session request, wherein the source IP session holding entry comprises an IP address of the client, an IP address of a server corresponding to the client, and the insert cookie;

if a second session request which does not carry the inserted cookie and is received from the client is received, executing corresponding session processing of source IP session maintenance on the second session request based on the source IP session maintenance table entry;

further comprising: and if a third session request carrying the inserted cookie is received from the client, forwarding the third session request to the IP address of the server corresponding to the inserted cookie.

2. The method of claim 1, wherein the source IP session holding entry comprises at least an IP address of a server corresponding to the client, and wherein performing session processing for the corresponding source IP session holding on the second session request based on the source IP session holding entry comprises:

3. The method of claim 2, further comprising:

4. The session processing device is applied to load balancing equipment in a load balancing system, and the load balancing system further comprises a client and a server; wherein, the client is connected with the server through the load balancing device for communication, and the device comprises:

a creating module that creates a source IP session holding entry corresponding to an inserted cookie of the first session request, wherein the source IP session holding entry includes an IP address of the client, an IP address of a server corresponding to the client, and the inserted cookie;

a session processing module, configured to, if a second session request that does not carry an inserted cookie is received from the client, perform, based on the source IP session holding entry, a session process of corresponding source IP session holding on the second session request;

the session processing module further: and if a third session request carrying the inserted cookie is received from the client, forwarding the third session request to the IP address of the server corresponding to the inserted cookie.

5. The apparatus of claim 4, wherein the source IP session holding entry comprises at least an IP address of a server corresponding to the client, and wherein the session processing module is further to:

6. The apparatus of claim 5, wherein the session processing module is further to:

7. An electronic device is characterized by comprising a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;

the memory has stored therein machine-readable instructions, the processor executing the method of any of claims 1 to 3 by calling the machine-readable instructions.

8. A machine-readable storage medium having stored thereon machine-readable instructions which, when invoked and executed by a processor, carry out the method of any of claims 1 to 3.