Browser optimization through user history analysis
The present invention relates to systems, apparatus, and methods of using real user history data to improve prefetching for a web page transaction. In one potential embodiment a method includes a proxy server observing a first web page transaction that has a first root HTTP request, a first root HTTP response, at least one child HTTP request, and at least one child HTTP response. The server may then extract a parameter from the web page transaction and correlating the parameter with the child HTTP request. In a later web page transaction, the parameter may be used to predict the child HTTP being requested even when the web page transactions are different.
1. A method comprising:
receiving, at a computing device, a web object from a content server;
determining, by the computing device, whether the web object is a root object or a child object;
responsive to determining that the web object is a child object, identifying, by the computing device, a first root object of a pending web page transaction, the web object requested as a part of the pending web page transaction; and
associating the web object with the pending web page transaction.
2. The method of claim 1 , wherein the computing device is a proxy server or a proxy client.
3. The method of claim 1 , wherein identifying the first root object comprises accessing a list of active root objects or a referral tree.
4. The method of claim 1 , wherein determining whether the web object is the root object or a child object of the pending web page transaction comprises determining whether the web object includes text information.
5. The method of claim 4 , further comprising scanning the text information.
6. The method of claim 4 , wherein the text information comprises HTML tags.
7. The method of claim 6 , further comprising, responsive to identifying a title HTML tag in the text information, determining the web object is the first root object.
8. The method of claim 7 , further comprising adding the first root object to a list of active root objects.
9. The method of claim 4 , further comprising, responsive to determining the web object does not include text information, determining the web object is a child object.
10. The method of claim 1 , wherein determining whether the web object is the root object or a child object of the pending web page transaction comprises determining whether web object comprises an HTTP 304 response.
11. The method of claim 10 , further comprising, responsive to determining the web object is the root object and that the web object comprises an HTTP 304 response:
accessing a tracking history for a uniform resource locator (“URL”) associated with the root object; and
prefetching one or more child objects associated with the URL.
12. A system comprising:
a non-transitory computer-readable medium; and
a processor in communication with the non-transitory computer-readable medium and configured to execute program code in the non-transitory computer-readable medium to:
receive, at a computing device, a web object from a content server;
determine, by the computing device, whether the web object is a root object or a child object; and
responsive to a determination that the web object is a child object, identify, by the computing device, a first root object of a pending web page transaction, the web object requested as a part of the pending web page transaction, and
associate the web object with the pending web page transaction.
13. The system of claim 12 , wherein the processor is further configured to execute program code in the non-transitory computer-readable medium to access a list of active root objects or a referral tree to identify the first root object.
14. The system of claim 12 , wherein the processor is further configured to execute program code in the non-transitory computer-readable medium to determining whether the web object includes text information.
15. The system of claim 14 , wherein the processor is further configured to execute program code in the non-transitory computer-readable medium to scan the text information.
16. The system of claim 14 , wherein the text information comprises HTML tags.
17. The system of claim 16 , wherein the processor is further configured to execute program code in the non-transitory computer-readable medium to, responsive to identifying a title HTML tag in the text information, determine the web object is the first root object.
18. The system of claim 14 , wherein the processor is further configured to execute program code in the non-transitory computer-readable medium to add the first root object to a list of active root objects.
19. The system of claim 14 , wherein the processor is further configured to execute program code in the non-transitory computer-readable medium to, responsive to a determination that the web object does not include text information, determine the web object is a child object.
20. The system of claim 12 , wherein the processor is further configured to execute program code in the non-transitory computer-readable medium to determine whether web object comprises an HTTP 304 response.
21. The system of claim 20 , wherein the processor is further configured to execute program code in the non-transitory computer-readable medium to, responsive to determining the web object is the root object and that the web object comprises an HTTP 304 response:
access a tracking history for a uniform resource locator (“URL”) associated with the root object; and
prefetch one or more child objects associated with the URL.
22. A non-transitory computer-readable medium comprising processor-executable program code configured to cause a processor to receive, at a computing device, a web object from a content server;
determine, by the computing device, whether the web object is a root object or a child object; and
responsive to a determination that the web object is a child object, identify, by the computing device, a first root object of a pending web page transaction, the web object requested as a part of the pending web page transaction, and
associate the web object with the pending web page transaction.
23. The non-transitory computer-readable medium of claim 22 , further comprising processor-executable program code configured to cause a processor to access a list of active root objects or a referral tree to identify the first root object.
24. The non-transitory computer-readable medium of claim 22 , further comprising processor-executable program code configured to cause a processor to determine whether the web object includes text information.
25. The non-transitory computer-readable medium of claim 24 , further comprising processor-executable program code configured to cause a processor to scan the text information.
26. The non-transitory computer-readable medium of claim 24 , wherein the text information comprises HTML tags.
27. The non-transitory computer-readable medium of claim 26 , further comprising processor-executable program code configured to cause a processor to, responsive to identification of a title HTML tag in the text information, determine the web object is the first root object.
28. The non-transitory computer-readable medium of claim 24 , further comprising processor-executable program code configured to cause a processor to add the first root object to a list of active root objects.
29. The non-transitory computer-readable medium of claim 24 , further comprising processor-executable program code configured to cause a processor to, responsive to a determination that the web object does not include text information, determine the web object is a child object.
30. The non-transitory computer-readable medium of claim 22 , further comprising processor-executable program code configured to cause a processor to determine whether web object comprises an HTTP 304 response.
31. The non-transitory computer-readable medium of claim 30 , further comprising processor-executable program code configured to cause a processor to, responsive to determining the web object is the root object and that the web object comprises an HTTP 304 response:
access a tracking history for a uniform resource locator (“URL”) associated with the root object; and
prefetch one or more child objects associated with the URL.