# US 10,771,581 B2 · Systems and methods for handling a cookie from a server by an intermediary between the server and a client

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,771,581 B2
- Document ID: US10771581B2
- Status: Granted
- Kind: B2
- Application number: 14/488,536
- Filed: 2014-09-17
- Published: 2015-03-26
- Granted: 2020-09-08
- Earliest claimed: 2013-09-20
- Assignees: Yottaa Inc.
- Applicants: Yottaa Inc.
- Inventors: Coach K. Wei; Robert Buffone
- Web page: https://patentgrep.com/patent/US10771581B2

## CPC

- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- G06F 9/46: Multiprogramming arrangements
- G06F 9/54: Interprogram communication
- G06F 16/00: Information retrieval; Database structures therefor; File system structures therefor
- G06F 40/143: Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/561: Adding application-functional data or data for application control, e.g. adding metadata
- H04L 67/564: Enhancement of application control based on intercepted application data
- H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561)
- G06F 2209/541: Client-server
- G06F 2209/542: Intercept
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

This disclosure is directed to methods and systems for handling a cookie by an intermediary between a server and a client. An intermediary may receive a first request from a client for a web page of a server, and may incorporate code into a first fragment of the web page to include in a modified web page for presentation at the client. The code, upon execution, may transmit a predefined request from the client. The intermediary may receive a response from the server to the first request. The response may include a cookie and information about the cookie in a header section of the response. The intermediary may transmit to the client responsive to the predefined request, the cookie and a second fragment for inclusion in the modified web page. The second fragment may include the information about the cookie in a header section of the second fragment.

## Claims

### Claim 1

A method for handling a cookie from a server by an intermediary between the server and a client, comprising:
(a) receiving, by an intermediary between a client and a server, a first request from the client for a web page of the server;
(b) transmitting, by the intermediary the first request to the server;
(c) incorporating, by the intermediary, code into a first fragment of the web page and transmitting the first fragment to the client to be included in a modified web page for presentation at the client, wherein the code, upon execution as the first fragment is presented to a user of the client, transmits a predefined request from the client;
(d) receiving, by the intermediary, a response from the server to the first request, the response comprising a cookie and information about the cookie in a header section of the response;
(e) receiving, by the intermediary, the predefined request from the client and determining, according to an identifying element in the predefined request that associates the predefined request to the cookie, that the predefined request is for prompting the intermediary to transmit to the client the cookie and the information about the cookie received in the response from the server; and
(f) transmitting, by the intermediary to the client responsive to the determination, the cookie and a second fragment for inclusion in the modified web page, the second fragment including the information about the cookie in a header section of the second fragment.

### Claim 2 (depends on 1)

The method of claim 1, comprising determining, by the intermediary, that the server provides a HttpOnly cookie.

### Claim 3 (depends on 1)

The method of claim 1, comprising determining, by the intermediary, that the server provides a HttpOnly cookie based on a prior communication from the server.

### Claim 4 (depends on 1)

The method of claim 1, wherein (b) comprises incorporating code that, upon execution, requests a predefined resource from the server.

### Claim 5 (depends on 1)

The method of claim 1, further comprising associating, by the intermediary, the predefined request with the server's response comprising the information about the cookie.

### Claim 6 (depends on 1)

The method of claim 1, wherein (f) comprises transmitting the second fragment, the second fragment comprising a multipurpose internet mail extensions (MIME) multipart message.

### Claim 7 (depends on 1)

The method of claim 1, wherein (f) comprises transmitting the second fragment, the second fragment comprising a body section that is empty or having a one-pixel image.

### Claim 8

A system for handling a cookie from a server by an intermediary between the server and a client, the system comprising:
code configured for executing on a client to transmit a predefined request from the client; and
an intermediary device, located between the client and a server, comprising:
one or more processors with executable instructions configured for:
receiving a first request from the client for a web page of the server;
transmitting the first request to the server;
incorporating the code into a first fragment of the web page and transmitting the first fragment to the client to be included in a modified web page for presentation at the client, wherein the code, upon execution as the first fragment is presented to a user of the client, transmits the predefined request;
receiving a response from the server to the first request, the response comprising a cookie and information about the cookie in a header section of the response;
receiving, by the intermediary, the predefined request from the client;
determining, according to an identifying element in the predefined request that associates the predefined request to the cookie, that the predefined request is for prompting the intermediary to transmit to the client the cookie and the information about the cookie received in the response from the server; and
transmitting to the client responsive to the determination, the cookie and a second fragment for inclusion in the modified web page, the second fragment including the information about the cookie in a header section of the second fragment.

### Claim 9 (depends on 8)

The system of claim 8, wherein the intermediary device determines that the server provides a HttpOnly cookie.

### Claim 10 (depends on 8)

The system of claim 8, wherein the intermediary device determines that the server provides a HttpOnly cookie based on a prior communication from the server.

### Claim 11 (depends on 8)

The system of claim 8, wherein the intermediary device incorporates code that, upon execution, requests a predefined resource from the server.

### Claim 12 (depends on 8)

The system of claim 8, wherein the intermediary device associates the predefined request with the server's response comprising the information about the cookie.

### Claim 13 (depends on 8)

The system of claim 8, wherein the intermediary device transmits the second fragment, the second fragment comprising a multipurpose internet mail extensions (MIME) multipart message.

### Claim 14 (depends on 8)

The system of claim 8, wherein the intermediary device transmits the second fragment, the second fragment comprising a body section that is empty or having a one-pixel image.