Method and system for acceleration of secure socket layer transactions in a network

• US 20050177866A1
• Filed: 02/09/2004
• Published: 08/11/2005
• Est. Priority Date: 02/09/2004
• Status: Abandoned Application

• Current Assignee: Propel Software Corporation (GlobalPOPs, Inc.)
• Original Assignee: Propel Software Corporation (GlobalPOPs, Inc.)
• Inventors: Kirsch, Steven T.
• Application Number:
  US10/775,804
• Publication Number:
  US 20050177866A1
• Time in Patent Office: Days
• US Class Current: 726/3
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0471 applying encryption by an intermediary, e.g. receiving clear information at the intermediary and encrypting the received information at the intermediary before forwarding
• CPC Class Codes: H04L 63/166 at the transport layer
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A system and method of accelerating delivery of SSL webpages. A client proxy associated with a client browser rewrites links to secure websites in a webpage before returning the webpage to the browser. The links are rewritten such that they are recognized and processed as a request for a secure webpage by another proxy in the network. The proxy returns the request to its original format and requests the page. The proxy establishes an SSL session with the server and decrypts and compresses the response before sending it to the client proxy, where the response is scanned for any links to secure webpages that should be rewritten before the response is returned to the client. This approach, which is transparent to the client, may be combined with other solutions, for instance, certain compression techniques and/or network architectures, for further reducing bandwidth and communication latency.

Claims

1. A method for accelerating delivery of requested secure webpages comprising:

a) receiving a request for a secure webpage, the request made using a link in a first received webpage which has been rewritten from an original format at a client proxy such that any request for the secure webpage made by referencing the rewritten link is recognized by a device intermediating between a client and a server capable of responding to the request for the secure webpage;

b) returning the request to its original format;

c) requesting the secure webpage from the server; and

d) receiving the secure webpage from the server.

2. The method of claim 1 further comprising scanning the first received webpage for any link to a secure webpage.

3. The method of claim 1 further comprising establishing a secure connection between the device and the server responding to the request for the secure webpage.

4. The method of claim 1 wherein an https request in the first received webpage is rewritten to be an http request.

5. The method of claim 1 wherein an https request in the first received webpage is rewritten to include a reference to a subdomain recognized by the device as indicating a request for a secure webpage.

6. The method of claim 5 further comprising establishing a secure connection between the client and the device when the request for the secure webpage is received at the device.

7. The method of claim 1 further comprising returning any received webpage to the client proxy.

8. The method of claim 1 further comprising returning any received webpage to the client.

9. The method of claim 1 further comprising decrypting the secure webpage.

10. The method of claim 1 further comprising compressing the secure webpage.

11. The method of claim 10 wherein compressing the secure webpage includes:

a) compressing data with software acting as an encoder, the software running on a first device in network communication with other devices, the compressed data to be transmitted to a second device in the network running software acting as a decoder, the compressing consisting of representing runs of data with at least one identifier;

b) storing the at least one identifier and corresponding data represented by the at least one identifier in a database associated with the encoder; and

c) transmitting from the encoder to the decoder data corresponding to the at least one identifier when the data is specifically requested by the decoder or when the encoder has no record of the at least one identifier being sent to the decoder.

12. The method of claim 11 further including representing runs of identifiers with a single identifier.

13. The method of claim 11 further including transmitting from the encoder to the decoder only data required to complete a response to the request where the data has not been cached at a second database associated with the decoder.

14. A method for accelerating delivery of requested secure webpages comprising:

a) scanning a webpage to determine whether it contains any links to at least one secure webpage;

b) rewriting any link to at least one secure webpage such that a request for the secure webpage made by referencing the rewritten link is recognized by a device intermediating between a client and a server capable of responding to the request for the secure webpage;

c) delivering the scanned webpage to the requesting client;

d) receiving a rewritten request for a secure webpage at the device, said request based on the rewritten link;

e) returning the request to its original format;

f) requesting the secure webpage from the server; and

g) receiving the requested webpage from the server.

15. The method of claim 14 wherein an https request is rewritten to be an http request.

16. The method of claim 14 wherein an https request is rewritten to include a reference to a subdomain recognized by the proxy as indicating a request for a secure webpage.

17. The method of claim 14 further comprising establishing a secure connection between the device and the server responding to the request for the secure webpage.

18. The method of claim 16 further comprising establishing a secure connection between the client and the device.

19. The method of claim 14 further comprising decrypting the received webpage.

20. The method of claim 14 further comprising compressing the received webpage.

21. The method of claim 14 further comprising returning the received webpage to the client proxy.

22. The method of claim 14 further comprising returning the received webpage to the client.

23. The method of claim 20 wherein compressing the secure webpage includes:

a) compressing data with software acting as an encoder, the software running on a first device in network communication with other devices, the compressed data to be transmitted to a second device in the network running software acting as a decoder, the compressing consisting of representing runs of data with at least one identifier;

b) storing the at least one identifier and corresponding data represented by the at least one identifier in a database associated with the encoder; and

c) transmitting from the encoder to the decoder data corresponding to the at least one identifier when the data is specifically requested by the decoder or when the encoder has no record of the at least one identifier being sent to the decoder.

24. The method of claim 23 further including representing runs of identifiers with a single identifier.

25. The method of claim 23 further including transmitting from the encoder to the decoder only data required to complete a response to the request where the data has not been cached at a second database associated with the decoder.

26. A system for accelerating delivery of requested secure webpages in a network comprising:

a) a client having software means for requesting and receiving secure and nonsecure webpages;

b) a plurality of servers having software means for responding to a client'"'"'s request for secure and nonsecure webpages;

c) a client proxy having means for rewriting links to any secure webpage in a webpage requested and received by the client, the links rewritten from their original format such that the client'"'"'s request for a secure webpage based on a rewritten link is recognized as a request for a secure webpage by a device intermediating between the client and the plurality of servers; and

d) a device intermediating between the client and the plurality of servers, the device having software means for recognizing the rewritten request for a secure webpage, returning the request to its original format, and using the original request to obtain the secure webpage from one of the plurality of servers.

27. The system of claim 26 further comprising the client proxy having means for delivering a requested webpage to the client.

28. The system of claim 26 further comprising the device having means for delivering a requested webpage to the client proxy.

29. The system of claim 26 further comprising the client proxy having means for scanning the received webpage for any links to a secure webpage.

30. The system of claim 26 further comprising the device having means for setting up a secure connection between the device and the server responding to the request for the secure webpage.

31. The system of claim 26 wherein the means for rewriting links to any secure webpage rewrites an https request is to be an http request.

32. The system of claim 31 wherein the means for rewriting links to any secure webpage rewrites an https request to include a reference to a subdomain recognized by the device as indicating a request for a secure webpage.

33. The system of claim 32 further comprising the client having means for establishing a secure connection between the client and the device.

34. The system of claim 26 wherein the client and device are members of a private network.

35. The system of claim 26 wherein the server is a member of a public network.

36. The system of claim 26 further comprising the device having means for decrypting the webpage.

37. The system of claim 26 further comprising the device having means for compressing the webpage.

38. The system of claim 37 further comprising the client proxy having means for decompressing the webpage.