IP Library Granted Patent US 10,068,014
Granted Patent B2
US 10,068,014 · App. 14/485,322 · Granted Sep 4, 2018

Security information management for content delivery

Inventors: Artur Bergman (San Francisco, CA); Tyler B. McMullen (San Francisco, CA)
Assignee: Fastly, Inc.
G06F17/30864G06F21/10H04L63/0892H04L67/2842
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,068,014
App. No.
14/485,322
Granted
Sep 4, 2018
Kind
B2
Abstract

Described herein are methods, systems, and software to handle verification information in a content node. In one example, a method of operating a content node includes receiving a secure content request from an end user device and determining the availability of verification information stored on the content node to service the secure content request. The method further provides, if the verification information is available, verifying the end user device based on the verification information. The method also includes, if the verification information is unavailable, querying an origin server to verify the end user device.

Claims (68)

1. A method of operating a content node that caches content in a content delivery network, the method comprising:

receiving a secure content request from an end user device for secure content;

determining if the requested secure content is available from cached content in the content node and if not, then retrieving the requested secure content from an origin server and caching the requested secure content in the content node;

determining if verification information is available from the content node:

if available, then verifying the end user device based on the verification information cached in the content node and transferring the requested secure content to the end user device from the content node; and

if not available, then:

requesting from the origin server to verify the end user device;

receiving new verification information from the origin server to verify the end user device after a subsequent secure content request;

caching the new verification information in the content node;

identifying an expiration of a time period for the new verification information to be valid from the origin server;

in response to the expiration of the time period, purging the new verification information; and wherein

if the verification information is available from the content node:

receiving a verification purge request; and

responsive to the verification purge request, purging the verification information.

2. The method of claim 1 further comprising:

in response to receiving the new verification information, transferring the requested secure content to the end user device.

3. The method of claim 1 further comprising:

in response to requesting the origin server to verify the end user device, transferring the requested secure content to the end user device from the content node.

4. The method of claim 1 further comprising:

receiving a second secure content request from the end user device prior to the expiration of the time period; and

in response to the second secure content request, verifying the end user device based on the new verification information cached in the content node.

5. The method of claim 4 further comprising:

in response to verifying the end user device based on the new verification information cached in the content node, transferring requested second secure content to the end user device.

6. The method of claim 1 wherein verifying the end user device based on the verification information cached in the content node comprises comparing security information from the end user device with the verification information cached in the content node.

7. The method of claim 1 wherein the verification information comprises cookie data.

8. The method of claim 1 wherein the secure content request comprises a request to access content in association with a paywall.

9. A non-transitory computer readable medium, comprising:

processing instructions stored on the non-transitory computer readable medium that, when executed by a content node, direct the content node to:

receive a secure content request from an end user device for secure content;

determine if the requested secure content is available from cached content in the content node and if not, then retrieve the requested secure content from an origin server and cache the requested secure content in the content node;

determine if verification information is available from the content node:

if available, then verify the end user device based on the verification information cached in the content node and transfer the requested secure content to the end user device;

if not available, then request the origin server to verify the end user device;

receive new verification information from the origin server to verify the end user device after a subsequent secure content request;

cache the new verification information for the end user device in the content node;

identify an expiration of a time period for the new verification information to be valid from the origin server;

in response to the expiration of the time period, purge the new verification information; and wherein

if the verification information is available from the content node:

receive a verification purge request; and

responsive to the verification purge request, purge the verification information.

10. The non-transitory computer readable medium of claim 9 wherein the processing instructions further direct the content node to:

in response to receiving the new verification information, transfer the requested secure content to the end user device.

11. The non-transitory computer readable medium of claim 9 wherein the processing instructions further direct the content node to:

receive a second secure content request from the end user device prior to the expiration of the time period; and

in response to the second secure content request, verify the end user device based on the new verification information cached in the content node.

12. The non-transitory computer readable medium of claim 11 wherein the processing instructions further direct the content node to:

in response to verifying the end user device based on the new verification information, transfer the requested second secure content to the end user device.

13. The non-transitory computer readable medium of claim 9 wherein the processing instructions to verify the end user device based on the verification information cached in the content node further direct the content node to:

compare security information from the end user device with the verification information cached in the content node.

14. The non-transitory computer readable medium of claim 9 wherein the verification information comprises cookie data.

15. The non-transitory computer readable medium of claim 9 wherein the secure content request comprises a request to access content in association with a paywall.

16. A content node for caching content in a content delivery network, the content node comprising:

a non-transitory computer readable storage medium;

a processing system communicatively coupled to the non-transitory computer readable storage medium;

processing instructions stored on the non-transitory computer readable storage medium that, when read and executed by the processing system, direct the processing system to:

receive a secure content request from an end user device for secure content;

determine if the requested secure content is available from cached content in the content node and if not, then retrieve the requested secure content from an origin server and cache the requested secure content in the content node;

determine if verification information is available from the content node:

if available, then verify the end user device based on the verification information cached in the content node and transfer the requested secure content to the end user device;

if not available, then request the origin server to verify the end user device;

receive new verification information from the origin server to verify the end user device after a subsequent secure content request;

cache the new verification information for the end user device in the content node;

identify an expiration of a time period for the new verification information to be valid from the origin server;

in response to the expiration of the time period, purge the new verification information; and wherein

if the verification information is available from the content node:

receive a verification purge request; and

responsive to the verification purge request, purge the verification information.

17. The content node of claim 16 wherein the verification information comprises cookie data.

Assignments (2)
SECURITY INTEREST Recorded Feb 17, 2021
From: FASTLY, INC.
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AND COLLATERAL AGENT
Reel/Frame 055316/0616 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 12, 2014
From: BERGMAN, ARTUR; MCMULLEN, TYLER B.
To: FASTLY, INC.
Reel/Frame 033733/0890 →
Continuity (2)
Provisional Application 61936440 · Feb 6, 2014
Related Publication 20150222642A1 · Aug 6, 2015