SYSTEMS AND METHODS FOR PREFETCHING NON-CACHEABLE CONTENT FOR COMPRESSION HISTORY

• US 20080228864A1
• Filed: 03/12/2007
• Published: 09/18/2008
• Est. Priority Date: 03/12/2007
• Status: Abandoned Application

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Inventors: Plamondon, Robert
• Application Number:
  US11/685,137
• Publication Number:
  US 20080228864A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/166 at the transport layer
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

The present solution provides a variety of techniques for accelerating and optimizing network traffic, such as HTTP based network traffic. The solution described herein provides techniques in the areas of proxy caching, protocol acceleration, domain name resolution acceleration as well as compression improvements. In some cases, the present solution provides various prefetching and/or prefreshening techniques to improve intermediary or proxy caching, such as HTTP proxy caching. In other cases, the present solution provides techniques for accelerating a protocol by improving the efficiency of obtaining and servicing data from an originating server to server to clients. In another cases, the present solution accelerates domain name resolution more quickly. As every HTTP access starts with a URL that includes a hostname that must be resolved via domain name resolution into an IP address, the present solution helps accelerate HTTP access. In some cases, the present solution improves compression techniques by prefetching non-cacheable and cacheable content to use for compressing network traffic, such as HTTP. The acceleration and optimization techniques described herein may be deployed on the client as a client agent or as part of a browser, as well as on any type and form of intermediary device, such as an appliance, proxying device or any type of interception caching and/or proxying device.

Claims

1. A method of prefetching non-cacheable content to store in a compression history to improve compression of subsequently transmitted pages having non-cacheable content, the method comprising the steps of:

(a) receiving, by a device, a first page transmitted by a server to a client, the first page identifying a non-cacheable object;

(b) generating, by the device, a request for the non-cacheable object identified by the page prior to a user requesting the non-cacheable object from the first page;

(c) transmitting, by the device, the generated request to the server; and

(d) storing, by the device, the non-cacheable object received from the server to a first compression history.

2. The method of claim 1, wherein step (a) comprises receiving, by the device, the first page transmitted via a first session of a user.

3. The method of claim 2, wherein the first page comprises a personalized version of a page for the user.

4. The method of claim 1, wherein the non-cacheable object is dynamically generated by the server.

5. The method of claim 1, comprising receiving, by the device, a second page transmitted by the server to the client, the second page comprising non-cacheable content.

6. The method of claim 5, comprising transmitting by the server the second page via one of a first session or a second session of a user.

7. The method of claim 6, wherein the second page comprises a personalized version of a page for the user.

8. The method of claim 5, comprising determining, by the device, a portion of the second page matches a portion of the non-cacheable object stored in the compression history.

9. The method of claim 8, comprising compressing, by the device in response to the determination, the second page using the matching portion of the non-cacheable object.

10. The method of claim 9, comprising transmitting, by the device, the compressed second page to the client.

11. The method of claim 10, receiving, by a second device, the compressed second page, and uncompressing the compressed second page using the matching non-cacheable object of the first page stored in a second compression history.

12. The method of claim 1, comprising receiving, by a second device, the first page forwarded by the device.

13. The method of claim 12, comprising transmitting, by the second device, a request generated by the second device to obtain from the server the non-cacheable object identified by the first page.

14. The method of claim 13, comprising storing, by the second device, to a second compression history the non-cacheable object received from the server in response to the generated request.

15. The method of claim 1, comprising receiving, by the device, via a plurality of user sessions a plurality of pages identifying a plurality of non-cacheable objects, transmitting a plurality of requests generated by the device to obtain the non-cacheable objects from one or more servers, and storing the plurality of non-cacheable objects received in response to the request to the first compression history.

16. The method of claim 15, comprising receiving, by the device, a third page, and determining a portion of the third page matches one or more portions of the plurality of non-cacheable objects stored in the first compression history.

17. The method of claim 1, wherein a portion of the compression history is stored in one of memory or disk storage.

18. The method of claim 1, comprising transmitting, by the device, at least a portion of the first compression history to a second device to store in a second compression history.

19. The method of claim 1, wherein the device comprises one of a client or an appliance.

20. A method of prefetching content via a network file transfer to use as a compression history for compressing Hypertext Protocol (HTTP) communications, the method comprising the steps of:

(a) executing a non-HTTP network file transfer of one or more files from a first device to a second device prior to a user requesting a file of the one or more files via an HTTP request;

(b) intercepting, by an appliance, packets of the non-HTTP network file transfer; and

(c) storing, by the appliance, content of the one or more files from the intercepted packets to a compression history.

21. The method of claim 20, comprising receiving, by the appliance, a page transmitted by a server to a client via an HTTP protocol in response to an HTTP request.

22. The method of claim 21, determining, by the appliance, a portion of the page matches at least a portion of the content of the one or more files stored in the first compression history.

23. The method of claim 22, comprising compressing, by the appliance, the page based on the determination.

24. The method of claim 23, comprising transmitting, by the appliance, the compressed page to the client.

25. The method of claim 24, comprising intercepting, by one of the client or a second appliance, the compressed page, and uncompressing the compressed page using one or more files from the network file transfer stored in a second compression history.

26. The method of claim 21, wherein the page comprises a file from the one or more files of the network file transfer.

27. The method of claim 20, comprising initiating, by an administrator of the appliance, execution of the network file transfer to preload the compression history of the appliance.

28. The method of claim 20, wherein the network file transfer comprises a remote file copy.

29. The method of claim 20, wherein the packets comprise one of a remote copy protocol or file transfer protocol.

30. The method of claim 20, comprising forwarding, by the appliance, the intercepted network packets to the second device.

31. The method of claim 20, comprising discarding, by the second device, the one or more files from the network file transfer.

32. The method of claim 20, intercepting, by a second appliance, the forwarded network packets, and storing content of the one or more files from the intercepted packets to a second compression history.

33. The method of claim 20, comprising initiating, by the appliance, execution of the network file transfer.

34. The method of claim 33, comprising initiating, by the appliance, execution of the network file transfer in response to a policy of a policy engine.