Managing Server Pushed Resources at Client

• US 20150229730A1
• Filed: 02/13/2014
• Published: 08/13/2015
• Est. Priority Date: 02/13/2014
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Loewenthal, Eric, Pashov, Ivan, Cox, Matthew
• Application Number:
  US14/180,199
• Publication Number:
  US 20150229730A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 63/1408 by monitoring network traffic monitoring network traffic per se H04L43/00
• CPC Class Codes: H04L 63/1441 Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

In one embodiment, a client device 110 may handle receiving pushed resources 452 from a server 120 at the client stack 114. The client stack 114 may send an initial navigation request 402 to a server 120 to initiate a navigation of the server. The client stack 114 may receive a pushed resource 452 from the server 120 processing the initial navigation request 402. The client stack 114 may match the pushed resource 452 to the initial navigation request 402.

Claims

1. A machine-implemented method, comprising:

sending an initial navigation request to a server to initiate a navigation of the server;

receiving a pushed resource at a client stack as part of the navigation of the server; and

matching the pushed resource to the initial navigation request.

2. The method of claim 1, further comprising:

placing the pushed resource in a virtual airlock.

3. The method of claim 1, further comprising:

promoting the pushed resource from a virtual airlock upon a trigger event.

4. The method of claim 1, further comprising:

prevent circumvention of a malware scan of the pushed resource.

5. The method of claim 1, further comprising:

receiving a linked resource request for the pushed resource.

6. The method of claim 1, further comprising:

checking for the pushed resource upon receiving a linked resource request.

7. The method of claim 1, further comprising:

providing a status description for the pushed resource to a user agent.

8. The method of claim 1, further comprising:

dropping a linked resource request upon detection of the pushed resource.

9. The method of claim 1, further comprising:

storing the pushed resource as an abstract connection object.

10. The method of claim 1, further comprising:

deleting the pushed resource upon a release event.

11. The method of claim 1, further comprising:

detecting at least one of a holding period expiration, a navigation termination, and a dirty malware scan as a release event.

12. A tangible machine-readable medium having a set of instructions detailing a method stored thereon that when executed by one or more processors cause the one or more processors to perform the method, the method comprising:

receiving a pushed resource as part of a navigation of a server;

placing the pushed resource in a virtual airlock; and

promoting the pushed resource from the virtual airlock upon a trigger event.

13. The tangible machine-readable medium of claim 12, wherein the method further comprises:

detecting at least one of a clean malware scan and a resource request for the pushed resource as the trigger event.

14. The tangible machine-readable medium of claim 12, wherein the method further comprises:

deleting the pushed resource upon a release event.

15. The tangible machine-readable medium of claim 12, wherein the method further comprises:

detecting at least one of a holding period expiration, a navigation termination, and a dirty malware scan as a release event.

16. The tangible machine-readable medium of claim 12, wherein the method further comprises:

matching the pushed resource to an initial navigation request to initiate the navigation of the server.

17. The tangible machine-readable medium of claim 12, wherein the method further comprises:

storing the pushed resource as an abstract connection object.

18. The tangible machine-readable medium of claim 12, wherein the method further comprises:

checking for the pushed resource upon receiving a linked resource request.

19. A client device, comprising:

a communication interface that sends an initial navigation request to a server to initiate a navigation of the server and receives a pushed resource;

a processor that matches the pushed resource to the initial navigation request; and

a memory that stores the pushed resource as an abstract connection object.

20. The client device of claim 19, wherein the memory places the pushed resource in a virtual airlock.