IDENTIFYING AND RESOLVING CACHE POISONING

• US 20140201457A1
• Filed: 01/16/2013
• Published: 07/17/2014
• Est. Priority Date: 01/16/2013
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Sinai, Eyal, Igelka, Or
• Granted Patent: US 9,230,037 B2
• Time in Patent Office: Days
• US Class Current: 711/135
• CPC Class Codes: G06F 12/121 using replacement algorithms
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

According to some embodiments, a method and apparatus are provided to receive, at a cache entity, a refresh request associated with a resource. A determination is made, via a processor, and based on the refresh request, to reload the resource from a server. The reloaded resource is replaced at the cache entity.

Claims

1. A method comprising:

receiving, at a cache entity, a refresh request associated with a particular resource;

determining, via a processor, and based on the refresh request, to reload the resource from a server; and

replacing the reloaded resource at the cache entity.

2. The method of claim 1, wherein the determining is further based on a predetermined number of refreshes coming from a predetermined number of clients.

3. The method of claim 1, wherein the determining is further based on exceeding a reliability score associated with the resource.

4. The method of claim 3, wherein the reliability score is incremented based on a number of received refresh requests.

5. The method of claim 4, wherein each received refresh request is weighted based on a client transmitting the received refresh request.

6. The method of claim 3, wherein the reliability score associated with the resource is based on an up-time of the server.

7. The method of claim 1, wherein the refresh request comprises an HTTP GET request, and wherein the HTTP GET request comprises a field indicating that the request is a refresh.

8. A non-transitory computer-readable medium comprising instructions that when executed by a processor perform a method, the method comprising:

receiving, at a cache entity, a refresh request associated with a particular resource;

determining, via a processor, and based on the refresh request, to reload the resource from a server; and

replacing the reloaded resource at the cache entity.

9. The medium of claim 8, wherein the determining is further based on a predetermined number of refreshes coming from a predetermined number of clients.

10. The medium of claim 8, wherein the determining is further based on exceeding a reliability score associated with the server.

11. The medium of claim 10, wherein the reliability score is incremented based on a number of received refresh requests.

12. The medium of claim 11, wherein each received refresh request is weighted based on a client transmitting the received refresh request.

13. The medium of claim 10, wherein the reliability score associated with the server is based on an up-time of the server.

14. The medium of claim 8, wherein the refresh request comprises an HTTP GET request, and wherein the HTTP GET request comprises a field indicating that the request is a refresh.

15. An apparatus comprising:

a processor;

a non-transitory computer-readable medium comprising instructions that when executed by the processor perform a method, the method comprising;

receiving, at a cache entity, a refresh request associated with a particular resource;

determining, via the processor, and based on the refresh request, to reload the resource from a server; and

storing the reloaded resource at the cache entity.

16. The apparatus of claim 15, wherein the determining is further based on a predetermined number of refreshes coming from a predetermined number of clients.

17. The apparatus of claim 15, wherein the determining is further based on exceeding a reliability score associated with the server.

18. The apparatus of claim 17, wherein the reliability score is incremented based on a number of received refresh requests.

19. The apparatus of claim 18, wherein each received refresh request is weighted based on a client transmitting the received refresh request.

20. The apparatus of claim 17, wherein the reliability score associated with the server is based on an up-time of the server.