SYSTEMS AND METHODS FOR USING AN HTTP-AWARE CLIENT AGENT

• US 20140344345A1
• Filed: 07/31/2014
• Published: 11/20/2014
• Est. Priority Date: 05/26/2005
• Status: Active Grant

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Inventors: He, Junxiao, Soni, Ajay, Stavrakos, Nicholas, Monks, Jeff, Koopmans, Fred, Koopmans, Chris, Dakhane, Kapil, Venkatraman, Charu
• Granted Patent: US 9,692,725 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/957 Browsing optimisation, e.g. caching or content distillation
• CPC Class Codes: H03M 7/30 Compression speech analysis-synthesis for redundancy reduction G10L19/00; for image communication H04N; Expansion; Suppression of unnecessary data, e.g. redundancy reduction
• CPC Class Codes: H04L 61/58 Caching of addresses or names
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 69/321 Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
• CPC Class Codes: H04W 8/245 from a network towards a terminal

Abstract

Systems and methods are described for using a client agent operating in a virtual private network environment to intercept HTTP communications. Methods include: intercepting at the network layer, by a client agent executing on a client, an HTTP request from an application executing on the client; modifying the HTTP request; and transmitting, via a transport layer connection, the modified HTTP request to a server. Additional methods may comprise adding, removing, or modifying at least one cookie in the HTTP request. Still other methods may comprise modifying at least one name-value pair contained in the HTTP request. Corresponding systems are also described.

Claims

1. A method comprising:

(a) intercepting, by a client agent executing on a client device, one or more transport layer packets below an application layer of a network stack of the client device, the one or more transport layer packets comprising application layer content data of a web page from a server for a request from a user agent executing on the client device;

(b) identifying, by the client agent operating below the application layer of the network stack of the client device, request object data from uniform resource locators (URLs) embedded in application layer content data contained in a payload of the intercepted one or more transport layer packets; and

(c) placing, by the client device, the request object data on a request object list;

(d) querying, by the client device, a data cache of the client device to determine whether the request object data of the request object list in stored in the data cache;

(e) marking, by the client device responsive to determining that request object data is not stored in the cache, in the request object list the request object data as to be downloaded to the client device; and

(e) transmitting, by the client device, the request object list to a second device.

2. The method of claim 1, wherein (a) further comprises intercepting, by the client agent, the one or more transport layer packets, at a network layer of the network stack.

3. The method of claim 1, wherein (a) further comprises intercepting, by the client agent, the one or more transport layer packets, at a transport layer of the network stack.

4. The method of claim 1, wherein (b) further comprises inserting, in the application layer content data, information identifying a version of the request object data identified by the URL stored in the data cache.

5. The method of claim 1, wherein (b) further comprises modifying a URL identified in the application layer content data.

6. The method of claim 1, wherein (d) further comprises determining that a second requested object data of the request object list is stored in the data cache and is fresh and wherein (e) further comprises marking the second requested object data in the request object list as being fresh.

7. The method of claim 1, wherein (d) further comprises determining that a second requested object data of the request object list is stored in the data cache and is stale;

and wherein (e) further comprises marking the second requested object data in the request object list as being stale.

8. The method of claim 1, wherein (e) further comprises determining that the requested object data marked as being stale or to be downloaded matches stored predicted request data in a predicted response cache.

9. The method of claim 8, further comprising marking the requested object data in the request object list as not to be downloaded.

10. The method of claim 1, wherein the second device is intermediary to the client device and a content server, the second device configured to obtain one or more requested object data in the request object list from one or more content servers.

11. A system comprising:

a client agent configured to execute on a processer of a client device and to intercept one or more transport layer packets below an application layer of a network stack of the client device, the one or more transport layer packets comprising application layer content data of a web page from a server for a request from a user agent executing on the client device;

wherein the client agent is configured to operate below the application layer of the network stack of the client device and to identify request object data from uniform resource locators (URLs) embedded in application layer content data contained in a payload of the intercepted one or more transport layer packets; and

wherein the client device is configured to place the request object data on a request object list and query a data cache of the client device to determine whether the request object data of the request object list in stored in the data cache; and

responsive to determining that request object data is not stored in the cache, the client device is configured to mark in the request object list the request object data as to be downloaded to the client device; and

wherein the client device is configured to transmit the request object list to a second device.

12. The system of claim 11, wherein the client agent is further configured to intercept the one or more transport layer packets, at a network layer of the network stack.

13. The system of claim 11, wherein the client agent is further configured to intercept the one or more transport layer packets, at a transport layer of the network stack.

14. The system of claim 11, wherein the client agent is further configured to insert in the application layer content data information identifying a version of the request object data identified by the URL stored in the data cache.

15. The system of claim 11, wherein the client agent is further configured to modify a URL identified in the application layer content data.

16. The system of claim 11, wherein the client device is further configured to determine that a second requested object data of the request object list is stored in the data cache and is fresh and mark the second requested object data in the request object list as being fresh.

17. The system of claim 11, wherein the client device is further configured to determine that a second requested object data of the request object list is stored in the data cache and is stale and mark the second requested object data in the request object list as being stale.

18. The system of claim 11, wherein the client device is further configured to determine that the requested object data marked as being stale or to be downloaded matches stored predicted request data in a predicted response cache.

19. The system of claim 18, wherein the client device is further configured to mark the requested object data in the request object list as not to be downloaded.

20. The system of claim 11, wherein the second device is intermediary to the client device and a content server, the second device is configured to obtain one or more requested object data in the request object list from one or more content servers.