TRANSPARENT PROXY CACHING OF RESOURCES

• US 20120239775A1
• Filed: 03/18/2011
• Published: 09/20/2012
• Est. Priority Date: 03/18/2011
• Status: Abandoned Application

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: HUBBARD, Robert, DAS, Ranadip
• Application Number:
  US13/051,342
• Publication Number:
  US 20120239775A1
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A device receives, from a client device, a request for a resource available from an origin device, and determines whether the resource is cached in a cache server. When the resource is cached, the device provides a first command instructing the client device to request the resource from the cache server, receives, from the client device, a first new request for the resource, and enables, based on the first new request, the client device to receive the resource from the cache server. When the resource is not cached, the device creates a firewall filter, provides a second command instructing the client device to request the resource from the origin device, receives, via the firewall filter and from the client device, a second new request for the resource, and enables, based on the second new request, the client device to receive the resource from the origin device.

Claims

1. A method performed by a computing device, the method comprising:

receiving, by the computing device and from a client device, a request for a resource available from an origin device;

determining, by the computing device, whether the resource is cached in a cache server or not cached in the cache server;

providing, by the computing device and when the resource is cached in the cache server, a first command instructing the client device to request the resource from the cache server;

receiving, by the computing device and from the client device, a first new request for the resource in response to providing the first command;

enabling, by the computing device and based on the first new request, the client device to receive the resource from the cache server;

creating, by the computing device and when the resource is not cached in the cache server, a firewall filter;

providing, by the computing device and when the resource is not cached in the cache server, a second command instructing the client device to request the resource from the origin device;

receiving, via the firewall filter and from the client device, a second new request for the resource in response to providing the second command; and

enabling, via the firewall filter and based on the second new request, the client device to receive the resource from the origin device without accessing the cache server.

2. The method of claim 1, further comprising:

removing the firewall filter after the client device receives the resource from the origin device.

3. The method of claim 2, where a cache hit/miss module, provided in the computing device, creates and removes the firewall filter.

4. The method of claim 3, where the cache hit/miss module is provided in a service plane of the computing device.

5. The method of claim 3, where the cache hit/miss module sends replies back to the client device until the cache hit/miss module determines that the request is one of a hypertext transfer protocol (HTTP) GET request or a HTTP HEAD request.

6. The method of claim 1, further comprising:

requesting that the cache server retrieve the resource from the origin device when the resource is not cached in the cache server.

7. The method of claim 1, where the firewall filter provides the second new request to the origin device, and the method further comprises:

receiving the resource from the origin device based on the second new request; and

forwarding the resource to the client device.

8. A network device, comprising:

a memory to store information regarding resources stored in a cache server; and

a processor to;

receive, from a client device, a request for a resource available from an origin device,

determine, based on the information, whether the resource is cached in the cache server or not cached in the cache server,

provide, when the resource is cached in the cache server, a first command instructing the client device to request the resource from the cache server,

receive, from the client device, a first new request for the resource in response to providing the first command,

enable, based on the first new request, the client device to receive the resource from the cache server,

create, when the resource is not cached in the cache server, a firewall filter,

provide, when the resource is not cached in the cache server, a second command instructing the client device to request the resource from the origin device,

receive, via the firewall filter and from the client device, a second new request for the resource in response to providing the second command,

enable, via the firewall filter and based on the second new request, the client device to receive the resource from the origin device without accessing the cache server, and

remove the firewall filter after the client device receives the resource from the origin device.

9. The network device of claim 8, where the processor is further to:

receive, from a client device, another request for another resource available from the origin device,

determine, based on the information, whether the other resource is cached in the cache server or not cached in the cache server,

provide, when the other resource is cached in the cache server, a third command instructing the client device to request the other resource from the cache server,

receive, from the client device, a third new request for the other resource in response to providing the third command, and

enable, based on the third new request, the client device to receive the other resource from the cache server.

10. The network device of claim 9, where the processor is further to:

re-create, when the other resource is not cached in the cache server, the firewall filter,

provide, when the other resource is not cached in the cache server, a fourth command instructing the client device to request the other resource from the origin device,

receive, via the firewall filter and from the client device, a fourth new request for the resource in response to providing the fourth command, and

enable, via the firewall filter and based on the fourth new request, the client device to receive the other resource from the origin device without accessing the cache server.

11. The network device of claim 8, where a cache hit/miss module, provided in the network device, creates and removes the firewall filter.

12. The network device of claim 11, where the cache hit/miss module is provided in a service plane of the network device.

13. The network device of claim 11, where the cache hit/miss module sends replies back to the client device until the cache hit/miss module determines that the request is one of a hypertext transfer protocol (HTTP) GET request or a HTTP HEAD request.

14. The network device of claim 8, where the processor is further to:

requesting that the cache server retrieve the resource from the origin device when the resource is not cached in the cache server.

15. One or more non-transitory computer-readable media storing instructions executable by one or more processors of a computing device, the media comprising:

one or more instructions to receive, from a client device, a request for a resource available from an origin device;

one or more instructions to determine whether the resource is cached in a cache server;

one or more instructions to provide, when the resource is cached in the cache server, a first command instructing the client device to request the resource from the cache server;

one or more instructions to receive, from the client device, a first new request for the resource in response to providing the first command;

one or more instructions to enable, based on the first new request, the client device to receive the resource from the cache server;

one or more instructions to create, when the resource is not cached in the cache server, a firewall filter;

one or more instructions to provide, when the resource is not cached in the cache server, a second command instructing the client device to request the resource from the origin device;

one or more instructions to receive, via the firewall filter and from the client device, a second new request for the resource in response to providing the second command; and

one or more instructions to enable, via the firewall filter and based on the second new request, the client device to receive the resource from the origin device without accessing the cache server.

16. The media of claim 15, where the media further comprises:

one or more instructions to remove the firewall filter after the client device receives the resource from the origin device.

17. The media of claim 15, where the media further comprises:

one or more instructions to implement a cache hit/miss module that creates and removes the firewall filter.

18. The media of claim 17, where the cache hit/miss module is provided in a service plane of the computing device.

19. The media of claim 17, where the request is one of a hypertext transfer protocol (HTTP) GET request or a HTTP HEAD request.

20. The media of claim 15, where the media further comprises:

one or more instructions to request that the cache server retrieve the resource from the origin device when the resource is not cached in the cache server.