System and method for performing application level persistence

• US 7,606,912 B1
• Filed: 03/09/2007
• Issued: 10/20/2009
• Est. Priority Date: 07/15/1999
• Status: Expired due to Fees

• Current Assignee: F5 Networks, Inc. (F5 Incorporated)
• Original Assignee: F5 Networks, Inc. (F5 Incorporated)
• Inventors: Masters, Richard Roderick
• Primary Examiner(s): VU, VIET DUY
• Application Number:
  US11/684,565
• Time in Patent Office: 956 Days
• Field of Search: 709/217, 709/219, 709/223, 709/225, 709/226, 709/227, 709/238
• US Class Current: 709/227
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1027 Persistence of sessions during load balancing
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

Abstract

A method and apparatus for inserting and examining Cookies in the data streams of HTTP connections for the purpose of persistently directing HTTP connections to the same destination. A network device directs subsequent HTTP connections from the same client to the same server (destination) for accessing the requested resources. There are four modes for employing the Cookie to persistently direct HTTP connections. The associated mode inserts a Cookie that uniquely identifies the client into an HTTP response. The passive mode inserts Cookie information that uniquely identifies a previously selected destination into an HTTP response. In the rewrite mode, a network device manages the destination information that is rewritten over blank Cookie information generated by the destination producing the HTTP response. The insert mode inserts and removes Cookie information in the data packets for HTTP requests and response prior to processing by the destination.

Claims

1. A method of enabling a load balancing system, comprising:

enabling a load balancer to load balance incoming client requests to a plurality of servers;

enabling each server of the plurality of servers to include blank persistence information as at least part of an application level protocol command in a response to a client request;

enabling the load balancer to receive the response to the client request from each of the plurality of servers, and to write persistence information that identifies the respective server in place of the blank persistence information; and

enabling the load balancer to recognize persistence information that is at least part of application level protocol commands included with incoming client requests, and to forward at least some incoming client requests having persistence information to one of the plurality of servers based at least in part on the persistence information included with the incoming client requests.

2. The method of claim 1, wherein the persistence information is included in an HTTP cookie command.

3. A device in a network that includes a plurality of clients and a plurality of servers, comprising:

a mechanism that receives a Hypertext Transport Protocol (HTTP) request from a client; and

a processor for enabling actions, including;

determining a destination server from the plurality of servers, based at least in part on a load balancing determination;

determining if the client previously communicated with the destination server, based at least in part on persistence information included in at least part of an application level protocol command, wherein the application level protocol command includes at least part of an HTTP cookie;

if it is determined that the client previously communicated with the destination server, determining the destination server based at least in part on the persistence information in the HTTP cookie; and

forwarding the HTTP request to the destination server.

4. The device of claim 3, further comprising commanding the client to create the HTTP cookie to include information identifying the destination server.

5. The device of claim 3, further comprising receiving the HTTP cookie from the destination server and inserting the persistence information in the HTTP cookie.

6. The device of claim 3, further comprising receiving the HTTP cookie form the destination server and rewriting at least a portion of the HTTP cookie to include the persistence information.

7. The device of claim 3, wherein the device is operational as at least one of a router, a load balancer, a switch, a server array controller, a server, and an intermediate network device.

8. The device of claim 3, wherein the HTTP cookie includes a key.

9. A system for load balancing communication in a network, comprising:

a plurality of clients;

a plurality of servers; and

a device that includes;

a mechanism arranged to receive a Hypertext Transport Protocol (HTTP) request from a client; and

a processor for enabling actions, including;

determining a destination server from the plurality of servers, based at least in part on a load balancing determination;

determining if the client previously communicated with the destination server, based at least in part on persistence information included in at least part of an application level protocol command, wherein the application level protocol command includes at least part of an HTTP cookie;

if it is determined that the client previously communicated with the destination server, determining the destination server based at least in part on the persistence information in the HTTP cookie; and

forwarding the HTTP request to the destination server.

10. The system of claim 9, further comprising commanding the client to create the HTTP cookie to include information identifying the destination server.

11. The system of claim 9, further comprising receiving the HTTP cookie from the destination server and inserting the persistence information in the HTTP cookie.

12. The system of claim 9, further comprising receiving the HTTP cookie form the destination server and rewriting at least a portion of the HTTP cookie to include the persistence information.

13. The system of claim 9, wherein the device is operational as at least one of a router, a load balancer, a switch, a server array controller, a server, and an intermediate network device.

14. The system of claim 9, wherein the HTTP cookie includes a key.