Method and system for determining receipt of a delayed cookie in a client-server architecture

• US 20030236862A1
• Filed: 06/21/2002
• Published: 12/25/2003
• Est. Priority Date: 06/21/2002
• Status: Active Grant

• Current Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Original Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Inventors: Moore, Mike, Miller, Lawrence, Deans, William
• Granted Patent: US 7,472,171 B2
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

In a client-server architecture, a semi-persistent connection between the client and the server allows delayed or asynchronous transmission of a cookie or token. Delayed or asynchronous transmission of the cookie allows initial web page generation and display while awaiting a slow cookie, such as a cryptographically generated cookie that might be used for single-session sign-on. A technique for determining whether the client has received the cookie is also provided.

Claims

1. A method for providing information to a client browser, the method comprising:

sending a request from a client to a server;

determining whether the request includes a token; and

if the token is not included in the request, determining whether the token is available to send to the client, wherein the token is created responsive to an earlier request from the client to the server.

2. A method according to claim 1, further comprising:

if the token is included in the request, making a record that the client has the token.

3. A method according to claim 1, further comprising:

if the token is available to send to the client, sending a response to the client with the token.

4. A method according to claim 1, further comprising:

if the token is not available to send to the client, sending a response to the client without the token.

5. A method according to claim 1, further comprising:

determining if a timer exceeds a predetermined value.

6. A method according to claim 5, further comprising:

if the timer does not exceed the predetermined value, determining whether the token is available to send to the client.

7. A method according to claim 5, further comprising:

if the timer does exceed the predetermined value, sending a response to the client without the token.

8. Computer executable software code transmitted as an information signal, the code for providing information to a client browser, the code comprising:

code to send a request from a client to a server;

code to determine whether the request includes a token; and

if the token is not included in the request, code to determine whether the token is available to send to the client, wherein the token is created responsive to an earlier request from the client to the server.

9. A computer readable medium having computer executable code stored thereon, the code for providing information to a client browser, the code comprising:

code to send a request from a client to a server;

code to determine whether the request includes a token; and

if the token is not included in the request, code to determine whether the token is available to send to the client, wherein the token is created responsive to an earlier request from the client to the server.

10. A programmed computer for providing information to a client browser, comprising:

a memory having at least one region for storing computer executable program code; and

a processor for executing the program code stored in the memory, wherein the program code comprises;

code for providing information to a client browser, the code comprising;

code to send a request from a client to a server;

code to determine whether the request includes a token; and

if the token is not included in the request, code to determine whether the token is available to send to the client, wherein the token is created responsive to an earlier request from the client to the server.