Mechanism for locking client requests to a particular server
First Claim
Patent Images
1. A method comprising:
- receiving a first request from a user corresponding to a first transaction at a dispatcher;
determining if the first transaction is a secure transaction;
creating at the dispatcher a secure tunnel context between the dispatcher and the user, if the transaction is a secure transaction, wherein the secure tunnel context comprises a session identifier (ID);
assigning a server to the first request at the dispatcher by adding an entry to a mapping table maintained by the dispatcher;
associating the session ID with the assigned server;
receiving a subsequent request from the user corresponding to a second transaction at the dispatcher, the subsequent request comprising the session ID;
determining if the session ID exists in the mapping table; and
sending the subsequent request to the assigned server if the session ID exists in the mapping table.
1 Assignment
0 Petitions
Accused Products
Abstract
In one aspect of the invention is a method for locking in all client requests having the same session I.D. to the same server to facilitate secure e-commerce transactions. A client'"'"'s session I.D. is mapped to an SSL context between a dispatcher and a server such that all subsequent client requests having the same session I.D. are forwarded to the same server.
-
Citations
26 Claims
-
1. A method comprising:
-
receiving a first request from a user corresponding to a first transaction at a dispatcher; determining if the first transaction is a secure transaction; creating at the dispatcher a secure tunnel context between the dispatcher and the user, if the transaction is a secure transaction, wherein the secure tunnel context comprises a session identifier (ID); assigning a server to the first request at the dispatcher by adding an entry to a mapping table maintained by the dispatcher; associating the session ID with the assigned server; receiving a subsequent request from the user corresponding to a second transaction at the dispatcher, the subsequent request comprising the session ID; determining if the session ID exists in the mapping table; and sending the subsequent request to the assigned server if the session ID exists in the mapping table. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. An article of manufacture including a machine readable medium having stored thereon data representing sequences of instructions, which, when executed by a machine, cause the machine to perform operations including:
-
receiving a first request from a user corresponding to a first transaction at a dispatcher; determining if the first transaction is a secure transaction; creating at the dispatcher a secure tunnel context between the dispatcher and the user, if the transaction is a secure transaction, wherein the secure tunnel context comprises a session identifier (ID); assigning a server to the first request at the dispatcher by adding an entry to a mapping table maintained by the dispatcher; associating the session ID with the assigned server;
receiving a subsequent request from the user corresponding to a second transaction at the dispatcher, the subsequent request comprising the session ID;determining if the session ID exists in the mapping table; and sending the subsequent request to the assigned server if the session ID exists in the mapping table. - View Dependent Claims (12, 13, 14, 15, 16)
-
-
17. A system comprising:
-
a mapping table at dispatcher, maintained by the dispatcher and containing session identifiers (IDs) linked to server and secure tunnel context assignments; and the dispatcher to receive a first request from a user corresponding to a first transaction to determine if the first transaction is a secure transaction, to create a secure tunnel context between the dispatcher and the user if the transaction is a secure transaction, wherein the secure tunnel context comprises a session identifier (ID), to assign a server to the first request by adding an entry to the mapping table, to associate the session ID with the assigned server, to receive a subsequent request from the user corresponding to a second transaction, the subsequent request comprising the session ID, to determine if the session ID exists in the mapping table, and send the subsequent request to the assigned server if the session ID exists in the mapping table. - View Dependent Claims (18, 19, 20, 21, 22)
-
-
23. A system comprising:
-
a load balancing table at a dispatcher and maintained by the dispatcher; a mapping table at the dispatcher and maintained by the dispatcher, the mapping table containing session identifiers (IDs) linked to server and secure tunnel context assignments; and the dispatcher to receive a first request from a user corresponding to a first transaction to determine if the first transaction is a secure transaction, to create a secure tunnel context between the dispatcher and the user, if the transaction is a secure transaction, wherein the secure tunnel context comprises a session identifier (ID), to assign a server to the first request by adding an entry to the mapping table, to associate the session ID with the assigned server, to receive a subsequent request from the user corresponding to a second transaction, the subsequent request comprising the session ID, to determine if the session ID exists in the mapping table, and send the subsequent request to the assigned server if the session ID exists in the mapping table. - View Dependent Claims (24, 25, 26)
-
Specification