Method and system for generating values for a request for caching of content items

• US 9,648,076 B2
• Filed: 01/08/2013
• Issued: 05/09/2017
• Est. Priority Date: 08/16/2000
• Status: Expired due to Fees

• Current Assignee: Parallel Networks, LLC (epicRealm Licensing LP)
• Original Assignee: Parallel Networks, LLC (epicRealm Licensing LP)
• Inventors: Saxena, Avinash C.
• Primary Examiner(s): Keehn, Richard G
• Application Number:
  US13/736,516
• Publication Number:
  US 20130124698A1
• Time in Patent Office: 1,582 Days
• Field of Search: 709217, 709216
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A web browser (20) at a client (12) generates a request (26) for content from an origin server (18). A cache server (16) intercepts the request and examines the request to determine whether the request should be transformed. More specifically, the cache server compares transform criteria (40) to a uniform resource identifier portion (28) and a header portion (30) associated with the request. By transforming the request such that information in the header portion is included in the uniform resource identifier portion, the cache server can cache the content associated with the request using the uniform resource identifier portion of the request.

Claims

1. A method for communicating data, comprising:

receiving a request comprising a uniform resource identifier and a header portion, the uniform resource identifier being associated with multiple content items that differ depending on information in the header portion, the request used in requesting a content item as specified by the uniform resource identifier and information in the header portion;

generating a value separate from the request using at least some of the information in the uniform resource identifier and at least some of the information in the header portion;

determining whether the content item is cached at a cache server using the value; and

retrieving the content item from the cache server if it is determined that the content item is cached.

2. The method of claim 1, wherein the value is a transformed URI.

3. The method of claim 1, further comprising:

retrieving the content item from an origin server if it is determined that the particular content item is not cached;

caching the content item at the cache server; and

storing the value assigned to the cached content item.

4. The method of claim 1, further comprising:

caching the content item at the cache server; and

storing the value assigned to the cached content item.

5. The method of claim 1, wherein the request is an HTTP request.

6. The method of claim 1, wherein the cache server is a combination of hardware and software.

7. The method of claim 1, wherein the content is dynamic content.

8. The method of claim 1, wherein cache server includes hardware or software.

9. A system for communicating data, comprising:

means for receiving a request comprising a uniform resource identifier and a header portion, the uniform resource identifier being associated with multiple content items that differ depending on information in the header portion, the request used in requesting a content item as specified by the uniform resource identifier and information in the header portion;

means for generating a value separate from the request using at least some of the information in the uniform resource identifier and at least some of the information in the header portion;

means for determining whether the content item is cached at a cache server using the value; and

means for retrieving the content item from the cache server if it is determined that the content item is cached.

10. The system of claim 9, wherein the value is a transformed URI.

11. The system of claim 9, further comprising:

means for retrieving the content item from an origin server if it is determined that the particular content item is not cached;

means for caching the content item at the cache server; and

storing the value assigned to the cached content item.

12. The system of claim 11, further comprising:

means for caching the content item at the cache server; and

means for storing the value assigned to the cached content item.

13. The system of claim 9, the request is an HTTP request.

14. The system of claim 9, wherein the cache server is a combination of hardware and software.

15. A non-transitory computer readable storage medium including code for communicating data, the code operable to:

receive a request comprising a uniform resource identifier and a header portion, the uniform resource identifier being associated with multiple content items that differ depending on information in the header portion, the request used in requesting a content item as specified by the uniform resource identifier and information in the header portion;

generate a value separate from the request using at least some of the information in the uniform resource identifier and at least some of the information in the header portion;

determine whether the content item is cached at a cache server using the value; and

retrieve the content item from the cache server if it is determined that the particular content item is cached.

16. The non-transitory computer readable storage medium of claim 15, wherein the value is a transformed URI.

17. The non-transitory computer readable storage medium of claim 15, wherein the code is further operable to:

retrieve the content item from an origin server if it is determined that the content item is not cached;

cache the content item at the cache server; and

store the value assigned to the cached content item.

18. The non-transitory computer readable storage medium of claim 15, wherein the code is further operable to:

cache the content item at the cache server; and

store the value assigned to the cached content item.