Transferring cookie data to another domain

Patent metadata

Field	Value
Publication number	US-2016261699-A1
Application number	US-201615152938-A
Country	US
Kind code	A1
Filing date	May 12, 2016
Priority date	Sep 20, 2011
Publication date	Sep 8, 2016
Grant date	—

Abstract

Disclosed are various embodiments for transferring cookie data between different domains. A first network data request is obtained from a client through a first domain. The first network data request includes a first cookie set by the first domain. Data from the first cookie is received from a client device along with a unique identifier through a first domain. A second network data request, which presents the unique identifier, is received from the client through a second domain. A second cookie is set in the client through the second domain based at least in part on data from the first cookie.

First claim

Therefore, the following is claimed:

1 . A non-transitory computer-readable medium embodying a program, that when executed in at least one computing device, causes the at least one computing device to at least:
receive, from a client device, a first request corresponding to a first domain, the first request including a unique identifier and data from a first cookie associated with the first domain, the first cookie being separate from the unique identifier; receive, from the client device, a second request corresponding to a second domain, the second request including the unique identifier; apply a transformation to at least a portion of the data from the first cookie to generate transformed data; and set a second cookie on the client device corresponding to the second domain, the second cookie containing the transformed data and excluding the unique identifier.

2 . The non-transitory computer-readable medium of claim 1 , wherein the at least a portion of the data from the first cookie and the second cookie are first-party cookies.

3 . The non-transitory computer-readable medium of claim 1 , wherein applying the transformation to generate the transformed data further causes the at least one computing device to at least:
determine a value at a first storage location of a first data store referenced in the at least a portion of the data from the first cookie; and identify a second storage location of the value in a second data store, the transformed data comprising the second storage location.

4 . The non-transitory computer-readable medium of claim 1 , wherein when executed the program further causes the at least one computing device to at least:
set the data in the first cookie associated with the first domain, the first cookie excluding the unique identifier; and generate a network page including code that, when executed by the client device, causes the client device to generate the unique identifier.

5 . The non-transitory computer-readable medium of claim 4 , wherein the network page further includes a first portion corresponding to the first domain and a second portion corresponding to the second domain.

6 . The non-transitory computer-readable medium of claim 5 , wherein the network page further includes code that, when executed by the client device, causes the client device to render the second portion corresponding to the second domain subsequent to setting the second cookie on the client device.

7 . A system, comprising:
a data store; and at least one computing device communicatively coupled to the data store, the at least one computing device being configured to at least:
receive, from a client device, a first request corresponding to a first domain, the first request including a unique identifier and a first cookie associated with the first domain;
store the first cookie in the data store associated with the unique identifier;
receive, from the client device, a second request corresponding to a second domain, the second request including the unique identifier and excluding the first cookie; and
set a second cookie on the client device corresponding to the second domain, the second cookie including data from the first cookie and excluding the unique identifier.

8 . The system of claim 7 , wherein the at least one computing device is further configured to at least:
receive, from the client device, a third request corresponding to the second domain, the third request including a second unique identifier and a third cookie associated with the second domain; store the third cookie in the data store associated with the second unique identifier; receive, from the client device, a fourth request corresponding to the first domain, the fourth request including the second unique identifier and excluding the third cookie; and set a fourth cookie on the client device corresponding to the first domain, the fourth cookie including data from the third cookie.

9 . The system of claim 7 , wherein the at least one computing device is further configured to at least execute a first network data service associated with the first domain and a second network data service associated with the second domain, the first network data service configured to receive the first request and the second network data service configured to receive the second request.

10 . The system of claim 7 , wherein the at least one computing device is further configured to at least generate the unique identifier and transmit the unique identifier to the client device.

11 . The system of claim 7 , wherein the at least one computing device is further configured to at least identify data corresponding to the first cookie in the data store based at least in part on the unique identifier in response to receiving the second request.

12 . The system of claim 7 , wherein the at least one computing device is further configured to at least determine a path corresponding to the first request based at least in part on a header of the first request, the path comprising the first domain and a first subdomain of the first domain.

13 . The system of claim 7 , wherein a first root path of the first domain corresponds to a first server and a second root path of the second domain corresponds to a second server, the first server and the second server being separate from the at least one computing device.

14 . The system of claim 7 , wherein the first cookie on the client device is inaccessible to the second domain.

15 . A method, comprising:
receiving, via at least one of one or more computing devices, a first command from a first server to set a first cookie associated with a first domain; generating, via at least one of the one or more computing devices, a unique identifier; sending, via at least one of the one or more computing devices, a first request to a subdomain of the first domain including the first cookie and the unique identifier, the subdomain corresponding to a second server; sending, via at least one of the one or more computing devices, a second request to at least one path of a second domain excluding the first cookie and including the unique identifier, the at least one path of the second domain corresponding to the second server; and receiving, via at least one of the one or more computing devices, a second command from the second server to set a second cookie associated with the second domain, the second cookie including data from the first cookie.

16 . The method of claim 15 , further comprising sending, via at least one of the one or more computing devices, a third request to a third server associated with the second domain for a network page, the third request including the second cookie associated with the second domain.

17 . The method of claim 15 , wherein the path of the at least one path corresponding to the second domain is a second subdomain of the second domain.

18 . The method of claim 17 , wherein the second server is a unitary network data server executing a first virtual host corresponding to the subdomain of the first domain and a second virtual host corresponding to the second subdomain of the second domain.

19 . The method of claim 15 , wherein the first cookie and the second cookie exclude the unique identifier.

20 . The method of claim 15 , wherein the data in the first cookie and data in the second cookie are identical.

Assignees

• Amazon Tech Inc

Inventors

• Martin Bobby D

Classifications

• H04L67/148

  Migration or transfer of sessions · CPC title

• H04L45/745

  Address table lookup; Address filtering · CPC title

• H04L67/146 Primary

  Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding · CPC title

• H04L41/0246

  Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols · CPC title