Method and system to detect a cached web page

• US 9,436,572 B2
• Filed: 06/02/2014
• Issued: 09/06/2016
• Est. Priority Date: 07/19/2007
• Status: Expired due to Fees

• Current Assignee: eBay Inc.
• Original Assignee: eBay Inc.
• Inventors: Choi, Gregory, Lagunas, Diego, Pottavathini, Sathishwar
• Primary Examiner(s): SHAW, PETER C
• Application Number:
  US14/293,925
• Publication Number:
  US 20140289317A1
• Time in Patent Office: 827 Days
• Field of Search: 709/203
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3037 where the computing system component is a memory, e.g. virtual memory, cache accessing, addressing or allocating within memory systems or architectures G06F12/00; checking stores for correct operation G11C29/00
• CPC Class Codes: G06F 12/0815 Cache consistency protocols
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

A method and system to determine whether a web page has been cached is provided. An example system comprises a cookie generator, a cookie distributor, and a cookie evaluator. The cookie distributor may be configured to provide the code to a client system, in response to a request for web content from the client system. A value of the code to be updated at the client system in response to the client system initiating a request for the web content. The cookie evaluator may be configured to compare a value of the code to the default value. The cached status detector may be configured to use a result of the comparing to determine a cached status of the web content, the cached status to indicate whether the web content has been cached by the client system.

Claims

1. A computer-implemented system comprising:

one or more processors provided at a server computer system;

a web page request detector, implemented using the one or more processors, to receive a request for web content and a client code from a client application executing at a client system, the client code includes an identifier associated with the requested web content;

a response generator, implemented using the one or more processors, to provide the web content to the client system, in response to the request from the client application, together with a request to set the client code at the client system to an uncached value;

an evaluator, implemented using the one or more processors, to compare the client code to the uncached value in response to detecting that the web content has been loaded at the client system; and

a cached status detector, implemented using the one or more processors, to determine that the web content has been cached by the client system, based on determining that the client code is distinct from the uncached value.

2. The system of claim 1, wherein:

the web content includes third party content associated with the identifier;

the request to set the client code to the uncached value includes setting the client code to the identifier;

the evaluator comparing the client code to the uncached value includes comparing the client code to the identifier in response to receiving, at the server computer system, a request for the third party content and the identifier; and

the cached status detector determining that the web content has been cached includes determining whether the request for the third party content is a request for new content based on determining that the client code is distinct from the identifier.

3. The system of claim 2, wherein the cached status detector is to determine that the request for the third party content is a new request based on the result of comparing of the value of the identifier stored in the client code at the client system and a previously stored third party content identifier being a match.

4. The system of claim 2, wherein the cached status detector is to determine that the request for the third party content is not a new request based on the result of comparing of the value of the identifier stored in the client code at the client system and a previously stored third party content identifier being a non-match.

5. The system of claim 2, wherein the third party content is an advertisement.

6. The system of claim 1, wherein the client code is to be modified at the client system in response to the client system initiating a request for the web content.

7. The system of claim 1, wherein the cached status detector is to determine that the web content has not been cached by the client system, based on determining that the value of the client code is the same as the uncached value.

8. The system of claim 1, comprising a code generator, implemented using one or more processors, to set a code to the uncached value at a server system.

9. The system of claim 1, comprising a code distributor, implemented using one or more processors, to provide the code to a client system as the client code.

10. The system of claim 1, wherein the web content is a web page.

11. A method comprising operations performed at a server computer system:

receiving a request for web content and a client code from a client application executing at a client system, the client code includes an identifier associated with the requested web content;

providing the web content to the client system, in response to the request from the client application, together with a request to set the client code at the client system to an uncached value;

comparing the client code to the uncached value in response to detecting that the web content has been loaded at the client system; and

determining, using one or more processors, that the web content has been cached by the client system, based on determining that the client code is distinct from the uncached value.

12. The method of claim 11, wherein:

the web content includes third party content associated with the identifier;

the request to set the client code to the uncached value includes setting the client code to the identifier;

the comparing the client code to the uncached value includes comparing the client code to the identifier in response to receiving, at the server system, a request for the third party content and the identifier; and

the determining that the web content has been cached includes determining whether the request for the third party content is a request for new content based on determining that the client code is distinct from the identifier.

13. The method of claim 12, wherein the determining that the request for the third party content is a new request is based on the result of comparing of the value of the identifier stored in the client code at the client system and a previously stored third party content identifier being a match.

14. The method of claim 12, wherein the determining that the request for the third party content is not a new request based on the result of comparing of the value of the identifier stored in the client code at the client system and a previously stored third party content identifier being a non-match.

15. The method of claim 12, wherein the third party content is an advertisement.

16. The method of claim 11, comprising modifying the value of the client code in response to the client system initiating a request for the web content.

17. The method of claim 11;

wherein the determining that the web content has not been cached by the client system, based on determining that the value of the client code is the same as the uncached value.

18. The method of claim 11, comprising setting a code to the uncached value at a server system.

19. The method of claim 11, comprising providing the code to a client system as the client code.

20. A machine-readable non-transitory storage medium having instruction data executable by a machine to cause the machine to perform operations comprising:

receiving a request for web content and a client code from a client application executing at a client system;

the client code includes an identifier associated with the requested web content;

providing the web content to the client system, in response to the request from the silent application;

together with a request to set the client code at the spent system to an uncached value;

comparing, at the server computer system;

a value of the client code to the uncached value in response to detecting that the web content has been loaded at the client system; and

determining that the web content has been cached by the client system, based on determining that the client code is distinct from the uncached value.