URL-based sticky routing tokens using a server-side cookie jar

• US 8,239,445 B1
• Filed: 04/25/2000
• Issued: 08/07/2012
• Est. Priority Date: 04/25/2000
• Status: Active Grant

• Current Assignee: A10 Networks Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Gage, Christopher A. S., Hind, John R., Peters, Marcia L.
• Primary Examiner(s): SHINGLES, KRISTIE D
• Application Number:
  US09/557,708
• Time in Patent Office: 4,487 Days
• Field of Search: 709/203, 709/217, 709/219, 709/225, 709/227, 709/228
• US Class Current: 709/203
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/10015 Access to distributed or replicated servers, e.g. using brokers
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method, system and program product are presented for enabling a session, as defined by a series of related transactions to perform a unit of work, to be created between a client and a particular server where the server is managed by a dispatcher. Modifications to the Uniform Resource Locator (URL) are used to create a method of transferring information form the client to the server. The server implements a server-side storage area (cookie jar) to temporarily store information about the client and the session so that the client is routed to the same server for successive messages in the same session and no reliance is made upon an ability by the client to store or return cookies.

Claims

1. A method of sending information to a requesting end user from an application over a session wherein said application resides at one of a plurality of redundant servers residing behind a network dispatcher, said method comprising the steps of:

receiving response information from said application, said response information including a URL (uniform resource locator);

determining if a server-side key cookie has been used for storing session information between said end user and said application;

if a server-side key cookie has been used for storing session information, retrieving a session key from said key cookie;

if a key cookie was not used for storing session information, retrieving said session key from a control block;

removing all cookies from said response information;

storing said removed cookies in a predetermined server-side storage area;

updating said URL to indicate the removal of said cookies;

creating a sticky routing string;

updating a date/time stamp in said sticky routing string;

inserting said sticky routing string into said URL; and

,

transmitting said response information, including said URL to said end user.

2. A method as claimed in claim 1 wherein, prior to said determining step, said response information is transmitted from said application through one or more filters.