Transparent session persistence management by a cache server in a content delivery network

• US 7,937,477 B1
• Filed: 06/09/2005
• Issued: 05/03/2011
• Est. Priority Date: 10/29/2004
• Status: Active Grant

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Kodialbail, Rekha, Liu, Zaide “Edward”, Swildens, Eric Sven-Johan, Day, Richard David
• Primary Examiner(s): Pwu; Jeffrey
• Assistant Examiner(s): Waqas; Saad A
• Application Number:
  US11/149,741
• Time in Patent Office: 2,154 Days
• Field of Search: 707/1, 707/200, 707/201, 707/10, 707/203, 707/101, 707/8, 707/102, 707/2, 713/153, 713/155, 713/151, 713/156, 713/160, 713/171, 713/185, 713/175, 713/183, 713/168, 370/401, 370/338, 380/30, 380/277, 726/12, 726/14, 705/26, 719/315, 719/316, 709/227
• US Class Current: 709/227
• CPC Class Codes: H04L 2463/101 applying security measures for digital rights management
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32

Abstract

A method and apparatus for establishing session persistence between a client and an origin server are provided. The session persistence can be managed by an intermediate cache server. The persistence is established by inserting an identifier and origin server address in a cookie or URL. Alternatively, the persistence is established by a table mapping a source IP address or a session ID to a specific origin server. Subsequent requests from the same client are mapped to the same origin server using these methods of establishing persistence.

Claims

1. A method of managing session persistence through a cache server in a content distribution network, comprising:

receiving, via a user interface and from an operator of an origin server associated with a domain name in a content distribution network, a selection of at least one persistence option from among a plurality of persistence options that include;

cache-server-based persistence, in which one or more cache servers in the content distribution network are responsible for establishing persistence, and origin-server-based persistence, in which one or more origin servers are responsible for establishing persistence;

wherein, for the selection by the operator of the origin server comprising cache-server-based-persistence, the one or more cache servers establishes an association between a client and an origin server by performing at least one action selected from a group of actions that are;

(i) with the one or more cache servers, sending a cookie to the client, the cookie including both an identifier indicating use of session persistence and an address associated with the origin server;

(ii) with the one or more cache servers, sending a URL to the client, the URL including both an identifier indicating use of session persistence and an address associated with the origin server;

(iii) with the one or more cache servers, entering a client IP address and the origin server address in a look-up table that associates the client with the origin server so as to establish session persistence; and

(iv) with the one or more cache servers, entering a SSL session identifier and the origin server address in a look-up table that associates the session with the origin server so as to establish session persistence;

wherein, for the selection by the operator of the origin server comprising origin-server-based persistence, the one or more origin servers establishes an association between a client and an origin server by performing at least one action selected from a group of actions that are;

(i) with the one or more origin servers, sending a cookie to the client via one or more cache servers, the cookie including both an identifier indicating use of session persistence and an address associated with the origin server; and

(ii) with the one or more origin servers, sending a URL to the client via one or more cache servers, the URL including both an identifier indicating use of session persistence and an address associated with the origin server;

receiving a first content request from the client at a cache server;

sending the first content request to an origin server selected by the cache server upon determining that the first content request cannot be satisfied by content in a cache associated with the cache server, wherein the cache server selects the origin server based on the association between the client and the origin server established according to the at least one persistence option selected by the operator of the origin server;

receiving first content at the cache server from the origin server in response to the first content request; and

sending the first content from the cache server to the client.

2. The method of claim 1, wherein the at least one persistence options is independently selectable for each of a plurality of sub-URLs associated with the domain name.

3. The method of claim 1, further comprising receiving, via the user interface and from the operator, a selection of at least one of cookie-based persistence, client-IP-based persistence, and URL-based persistence.

4. The method of claim 1, wherein the step of receiving the first content request from the client comprises receiving a request for static content.

5. The method of claim 1, wherein the step of receiving the first content request from the client comprises receiving a request for dynamic content.

6. The method of claim 1, further comprising:

determining that the client does not have an association with any origin server; and

selecting, with the cache server, an origin server from a plurality of origin servers associated with a specific domain name.

43. The method of claim 1, wherein the at least one selected persistence option comprises a cache-server-based persistence selection.

7. A method of operating cache servers in a content distribution network comprising:

receiving, via a user interface and from an operator of an origin server associated with a domain name in a content distribution network, a selection of a persistence option that comprises cache-server-based persistence, in which one or more cache servers in the content distribution network are responsible for establishing persistence by sending a client at least one of (i) a cookie including an identifier indicating use of session persistence and an address associated with an origin server, and (ii) a URL including an identifier indicating use of session persistence and an address associated with an origin server;

receiving a first request for content from a client at a first cache server in a content distribution network;

sending the first request for content to an origin server upon determining that the first request for content from the client cannot be satisfied with content stored in a first cache associated with the first cache server;

receiving and storing first content from the origin server at the first cache server;

sending the first content received from the origin server to the client;

sending the identifier and the origin server'"'"'s address to the client;

receiving a second request for content from the client at a second cache server in the content distribution network;

sending a second request for content to the origin server upon determining that the second request for content from the client cannot be satisfied with content in a second cache associated with the second cache server and upon determining from the identifier that persistence is being used;

receiving second content at the second cache server from the origin server;

sending the second content received from the origin server to the client; and

upon detection of a failure condition of the origin server by the second cache server, selecting, by the second cache server, a new origin server and sending, by the second cache server, the new origin server address to the client.

8. The method of claim 7, wherein the step of receiving the first request for content comprises receiving a request for dynamic content.

9. The method of claim 7, wherein the step of receiving the first request for content comprises receiving a request for static content.

10. The method of claim 7, wherein the step of sending the first request for content to the origin server comprises selecting the origin server based upon a load-balancing algorithm.

11. The method of claim 7, wherein the step of sending identifier and the origin server'"'"'s address to the client comprises inserting the identifier and the origin server'"'"'s address in a cookie and sending the cookie to the client.

12. The method of claim 11, wherein, in the step of sending the second request for content, the second cache server determines that the client is bound to the origin server from the cookie.

13. The method of claim 11, wherein the step of sending the new origin server address to the client upon determining that the origin server has failed further comprises inserting a new origin server address into the cookie and sending the cookie to the client upon determining that the origin server has failed.

14. The method of claim 7, wherein the step of sending the identifier and the origin server'"'"'s address to the client comprises inserting the identifier and the origin server address in a URL parameter.

15. The method of claim 14, wherein, in the step of sending the second request for content, the second cache server determines that the client is bound to the origin server from the URL parameter.

16. The method of claim 7, further comprising:

inserting the new origin server address into a URL parameter and sending the URL to the client upon detection of the failure of the origin server.

44. The method of claim 7, wherein the sending of the origin server'"'"'s address and at least one of a client IP address and a SSL session identifier to the client is performed by the first cache server.

17. A method of operating cache servers in a content distribution network comprising:

receiving, via a user interface and from an operator of an origin server associated with a domain name in a content distribution network, a selection of a persistence option that comprises cache-server-based persistence, in which one or more cache servers in the content distribution network are responsible for establishing persistence by performing at least one action selected from a group of actions that are;

(i) entering a client IP address and an origin server address in a look-up table; and

(ii) entering a SSL session identifier and an origin server address in a look-up table;

receiving a first request for content from a client at a first cache server in a content distribution network;

sending the first request for content to an origin server upon determining that the first request for content from the client cannot be satisfied with content stored in a first cache associated with the first cache server;

receiving, at the first cache server, first content from the origin server;

sending the first content received from the origin server to the client;

inserting the origin server'"'"'s address and at least one of a client IP address and a SSL session identifier in a table on the cache server;

distributing the table to at least one other cache server in the content distribution network;

receiving a second request for content from the client at a second cache server in the content distribution network;

sending a second request for content to the origin server upon determining that the second request for content from the client cannot be satisfied with content in a second cache associated with the second cache server and upon determining from the table that persistence is being used;

receiving second content at the second cache server from the origin server; and

sending the second content received from the origin server to the client; and

upon detection of a failure condition of the origin server by a cache server in the content distribution network, selecting, by the cache server that detected the origin server failure, a new origin server and inserting, by the cache server that detected the origin server failure, a new origin server address in the table.

18. The method of claim 17, wherein the step of receiving the first request for content comprises receiving a request for dynamic content.

19. The method of claim 17, wherein the step of receiving the first request for content comprises receiving a request for static content.

20. The method of claim 17, wherein the step of sending the first request for content to the origin server comprises selecting the origin server based upon a load-balancing algorithm.

21. The method of claim 17, wherein the step of distributing the table to at least one other cache server in the content distribution network comprises distributing the table to a subset of cache servers in the content distribution network.

22. The method of claim 17, wherein, in the step of sending the second request for content, the second cache server determines that the client is bound to the origin server by a look-up in the table.

23. The method of claim 22, wherein the step of inserting the origin server'"'"'s address and at least one of a client IP address and a SSL session identifier in the table on the cache server comprises inserting a masked version of a client IP address associated with the client in the table.

24. A cache server in a content distribution network, comprising:

a subsystem that receives, via a user interface and from an operator of an origin server associated with a domain name in a content distribution network, a selection of at least one persistence option from among a plurality of persistence options that includes;

cache-server-based persistence in which one or more cache servers in the content distribution network are responsible for establishing persistence, and origin-server-based persistence, in which one or more origin servers are responsible for establishing persistence;

wherein, for the selection by the operator of the origin server comprising cache-server-based-persistence, the one or more cache server'"'"'s subsystems establishes an association between a client and an origin server by performing at least one action selected from a group of actions that are;

(i) with the one or more of the cache server'"'"'s subsystems, sending a cookie to the client, the cookie including both an identifier indicating use of session persistence and an address associated with the origin server;

(ii) with the one or more of the cache server'"'"'s subsystems, sending a URL to the client, the URL including both an identifier indicating use of session persistence and an address associated with the origin server;

(iii) with one or more of the cache server'"'"'s subsystems, entering a client IP address and the origin server address in a look-up table that associates the client with the origin server so as to establish session persistence; and

(iv) with the one or more cache servers, entering a SSL session identifier and the origin server address in a look-up table that associates the session with the origin server so as to establish session persistence;

wherein, for the selection by the operator of the origin server comprising origin-server-based persistence, the one or more origin server'"'"'s subsystems establishes an association between a client and an origin server by performing at least one action selected from a group of actions that are;

(i) with the one or more origin server'"'"'s subsystems, sending a cookie to the client via one or more cache servers, the cookie including both an identifier indicating use of session persistence and an address associated with an origin server; and

(ii) with the one or more origin server'"'"'s subsystems, sending a URL to the client via one or more cache servers, the URL including both an identifier indicating use of session persistence and an address associated with an origin server;

a subsystem that receives a first content request from the client at a cache server;

a subsystem that sends the first content request to an origin server upon determining that the first content request cannot be satisfied by content in a cache associated with the cache server, wherein the cache server selects the origin server based on the association between the client and the origin server established according to the at least one persistence option selected by the operator of the origin server;

a subsystem that receives first content at the cache server from the origin server in response to the first content request; and

a subsystem that sends the first content to the client.

25. The cache server of claim 24, wherein the at least one persistence option is independently selectable for each of a plurality of sub-URLs associated with the domain name.

26. The cache server of claim 24, further comprising a subsystem that receives, via the user interface and from the operator, a selection of at least one of:

cookie-based persistence, client IP-based persistence, and URL-based persistence.

27. The cache server of claim 24, wherein the subsystem that receives the first content request from the client is configured to receive a request for static content.

28. The cache server of claim 24, wherein the subsystem that receives the first content request from the client is configured to receive a request for dynamic content.

29. The cache server of claim 24, further comprising:

a subsystem that determines that the client does not have an association with any origin server; and

a subsystem that selects an origin server from a plurality of origin servers associated with a specific domain name.

45. The apparatus of claim 24, wherein the at least one selected persistence option comprises cache-server-based persistence.

30. A content distribution network having a plurality of cache servers, comprising:

a subsystem that receives, via a user interface and from an operator of an origin server associated with a domain name in a content distribution network, a selection of a persistence option that comprises cache-server-based persistence, in which one or more cache servers in the content distribution network are responsible for establishing persistence by sending a client at least one of (i) a cookie including both an identifier indicating use of session persistence and an address associated with an origin server, and (ii) a URL including both an identifier indicating use of session persistence and an address associated with an origin server;

a subsystem that receives a first request for content from a client at a first cache server;

a subsystem that sends the first request for content to an origin server upon determining that the first request for content from the client cannot be satisfied with content stored in a first cache associated with the first cache server;

a subsystem that receives and stores first content from the origin server at the first cache server;

a subsystem that sends the first content received from the origin server to the client;

a subsystem that sends the identifier and the origin server'"'"'s address to the client;

a subsystem that receives a second request for content from the client at a second cache server in the content distribution network;

a subsystem that sends a second request for content to the origin server upon determining that the second request for content from the client cannot be satisfied with content in a second cache associated with the second cache server and upon determining from the identifier that persistence is being used;

a subsystem that receives second content at the second cache server from the origin server;

a subsystem that sends the second content received from the origin server to the client; and

a subsystem that, upon detection of a failure condition of the origin server by the second cache server, selects, with the second cache server, a new origin server and sends, with the second cache server, the new origin server address to the client.

31. The content distribution network of claim 30, wherein the subsystem that receives the first request for content is configured to receive a request for dynamic content.

32. The content distribution network of claim 30, wherein the subsystem that receives the first request for content is configured to receive a request for static content.

33. The content distribution network of claim 30, wherein the subsystem that sends the first request for content to the origin server is configured to select the origin server based upon a load-balancing algorithm.

34. The content distribution network of claim 30, wherein the subsystem that sends the new origin server address to the client upon detection of the failure condition of the origin server is configured to insert the new origin server address into a cookie and send the cookie to the client upon determining that the origin server has failed.

35. The content distribution network of claim 30, further comprising:

a subsystem that inserts the new origin server address into a URL parameter and sends the URL to the client upon detection of the failure of the origin server.

36. A content distribution network having a plurality of cache servers, comprising:

a subsystem that receives, via a user interface and from an operator of an origin server associated with a domain name in a content distribution network, a selection of a persistence option that comprises cache-server-based persistence, in which one or more cache servers in the content distribution network are responsible for establishing persistence by performing at least one action selected from a group of actions that are;

(i) entering a client IP address and an origin server address in a look-up table; and

(ii) entering a SSL session identifier and an origin server address in a look-up table;

a subsystem that receives a first request for content from a client at the first cache server;

a subsystem that sends first request for content to an origin server upon determining that the first request for content from the client cannot be satisfied with content stored in a first cache associated with the first cache server;

a subsystem that receives, at the first cache server, first content from the origin server;

a subsystem that sends the first content received from the origin server to the client;

a subsystem that inserts the origin server'"'"'s address and at least one of a client IP address and a SSL session identifier in a table on the cache server;

a subsystem that distributes the table to at least one other cache server in the content distribution network;

a subsystem that receives a second request for content from the client at a second cache server that is in the set of cache servers in the content distribution network;

a subsystem that sends a second request for content to the origin server upon determining that the second request for content from the client cannot be satisfied with content in a second cache associated with the second cache server and upon determining from the table that persistence is being used;

a subsystem that receives second content at the second cache server from the origin server; and

a subsystem that sends the second content received from the origin server to the client; and

a subsystem that, upon detection of a failure condition of the origin server by a cache server in the content distribution network, selects, by the cache server that detected the origin server failure, a new origin server and inserts, by the cache server that detected the origin server failure, a new origin server address in the table.

37. The content distribution network of claim 36, wherein the subsystem that receives the first request for content is configured to receive a request for dynamic content.

38. The content distribution network of claim 36, wherein the subsystem that receives the first request for content is configured to receive a request for static content.

39. The content distribution network of claim 36, wherein the subsystem that sends the first request for content to the origin server is configured to select the origin server based upon a load-balancing algorithm.

40. The content distribution network of claim 36, wherein the subsystem that distributes the table to at least one other cache server in the content distribution network is configured to distribute the table to a subset of cache servers in the content distribution network.

41. The content distribution network of claim 36, wherein, in the subsystem that sends the second request for content, the second cache server determines that the client is bound to the origin server by a look-up in the table.

42. The content distribution network of claim 41, wherein the subsystem that inserts the origin server'"'"'s address and at least one of a client IP address and a SSL session identifier in a table on the cache server is configured to insert a masked version of a client IP address associated with the client in the table.