PROXY SERVER CONFIGURED FOR HIERARCHICAL CACHING AND DYNAMIC SITE ACCELERATION AND CUSTOM OBJECT AND ASSOCIATED METHOD

• US 20120089700A1
• Filed: 10/10/2010
• Published: 04/12/2012
• Est. Priority Date: 10/10/2010
• Status: Abandoned Application

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Contendo, Inc.
• Inventors: Safruti, Ido, Trugman, Udi, Drai, David, Zehavi, Ronni
• Application Number:
  US12/901,571
• Publication Number:
  US 20120089700A1
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

A method is provided to deliver content over a network comprising: receiving a request by a proxy server; determining by the proxy server whether the received request involves content to be delivered from an origin using one or more persistent network connections or from a cache; sending by the proxy server a request to retrieve the content from a cache when the request is determined to involve cached content; and sending by the proxy server a request using one or more persistent network connections to retrieve the content from the origin when the content is to be is determined to involve content to be delivered using one or more persistent network connections.

Claims

1. (canceled)

2. An article of manufacture including a computer readable storage device encoded with instructions to cause a machine that includes processing and memory resources to perform a method including:

providing in a storage device a queue of respective tasks that correspond to respective requests for content received over the internet;

providing in the storage device respective configuration files that include parameters to evaluate whether respective received requests for content are for content that is cacheable or that is dynamic and to identify respective custom objects;

wherein running a respective task includes acts of,

comparing information from a respective received request for content corresponding to the respective task with parameters in a respective configuration file to determine whether the requested content is for cacheable content or dynamic content and to identify a custom object;

in response to a determination that the respective received request is for cacheable content, determining whether the requested content is cacheable on the respective server and when the content is determined to not be cacheable on the respective server, determining one of either another server in a content delivery network or an origin server from which to request the requested content, and producing a request by the server for transmission over the internet to request the requested content from a determined server, and receiving a response to the request; and

in response to a determination that the respective received request is for dynamic content, determining one of another server from among the respective servers in the content delivery network or the origin server to which to direct a request for the dynamic content, and producing a request by the server for transmission over the internet to request the requested content from a determined another server or the origin server, and receiving a response to the request; and

running the identified custom object in the course of running the respective task to affect one or more acts of the respective task.

3. The method of claim 2,

wherein affecting one or more acts of the respective task includes blocking the request.

4. The method of claim 2,

wherein affecting one or more acts of the respective task includes generating a response page and serving the page directly.

5. The method of claim 2,

wherein affecting one or more acts of the respective task includes rewriting the respective received request.

6. The method of claim 2,

wherein affecting one or more acts of the respective task includes sending a response to redirect to a different URL.

7. The method of claim 2,

wherein the act of determining whether the requested content is cacheable involves creating a cacheable key;

wherein affecting one or more acts of the respective task includes adding a user-agent to a cacheable key.

8. The method of claim 2,

wherein the act of determining whether the requested content is cacheable involves creating a cacheable key;

wherein affecting one or more acts of the respective task includes adding a cookie value to a cacheable key.

9. The method of claim 2,

wherein the act of determining whether the requested content is cacheable involves creating a cacheable key;

wherein affecting one or more acts of the respective task includes processing a URL to determine a cacheable key.

10. The method of claim 2,

wherein affecting one or more acts of the respective task includes adding an HTTP header to a request that is produced by the server in the course of running the respective task.

11. The method of claim 2,

wherein affecting one or more acts of the respective task includes changing an origin address within a request that is produced by the server in the course of running the respective task.

12. The method of claim 2,

wherein affecting one or more acts of the respective task includes changing a host string within a request that is produced by the server in the course of running the respective task.

13. The method of claim 2,

wherein affecting one or more acts of the respective task includes adding a geo based replacement string to a response to the request that is received by the server in the course of running the respective task.

14. The method of claim 2,

wherein affecting one or more acts of the respective task includes inserting personalized information to a web page that is received by the server in the course of running the respective task.

15. The method of claim 2,

wherein affecting one or more acts of the respective task includes pre-fetching objects based upon a response received by the server in the course of running the respective task.

16. The method of claim 2,

wherein affecting one or more acts of the respective task includes triggering a new request based upon a response received by the server in the course of running the respective task.

17. The method of claim 16,

wherein the new request includes a request for personalized data for a web page.

18. The method of claim 16,

wherein the new request includes a request to a merchant that includes a token to indicate that credit card authorization has been obtained.

19. The method of claim 16,

wherein the new request includes a request to an alternate server.

20. The method of claim 2,

wherein affecting one or more acts of the respective task includes adding compression to a response to the request that is received by the server in the course of running the respective task.

21. The method of claim 2,

wherein affecting one or more acts of the respective task includes adding debug information to a response to the request that is received by the server in the course of running the respective task.

22. The method of claim 2,

wherein affecting one or more acts of the respective task includes adding flow information to a response to the request that is received by the server in the course of running the respective task.

23. The method of claim 2,

wherein affecting one or more acts of the respective task includes adding flow information to a response to the request that is received by the server in the course of running the respective task.

24. The method of claim 2,

wherein affecting one or more acts of the respective task includes adding cacheable status to a response to the request that is received by the server in the course of running the respective task.

25. The method of claim 2,

wherein affecting one or more acts of the respective task includes modifying an HTML page within a response to the request that is received by the server in the course of running the respective task.

26. The method of claim 25,

wherein modifying the HTML page within the response includes optimizing one or more URLs within the HTML page based upon device or upon location.

27. The method of claim 25,

wherein modifying the HTML page within the response includes obtaining information from a cookie in the request and including that information in the HTML page.

28. The method of claim 27,

wherein the information from the cookie includes a user name.