Browser-plugin based method for advanced HTTPS data processing

• US 20060155869A1
• Filed: 12/22/2005
• Published: 07/13/2006
• Est. Priority Date: 12/22/2004
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: SlipStream Data Incorporated (Blackberry Limited)
• Inventors: Singh, Ajit, Ahmed, Salmaan, Sze, David, Nanduri, Akshay
• Granted Patent: US 7,634,572 B2
• Time in Patent Office: Days
• US Class Current: 709/232
• 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]
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC

Abstract

The invention described here deals with implementing custom data processing of HTTPS based on a Browser-Plugin Method. Stich custom data processing may include, but is not limited to, custom data compression, custom data encryption, data monitoring, data modification. There are two distinct methods to implement the Browser-Plugin Method for Advanced HTTPS Data Processing of the subject invention (BPAHDP). In both cases, BPAHDP provides the option of conducting custom data processing that co-exists with data compression, data encryption, or other types of data processing operations supported by the HTTP standard. Additionally, both BPAHDP methods ensure that the web-browser still implements and executes the underlying SSL/TLS channel setup and encryption operations. In both embodiments of BPAHDP, the most critical functionality is the ability to modify HTTP request/response headers and data sent over a TLS/SSL channel. In the regular. HTTP case (HTTP over TCP) headers and data are sent as clear-text (i.e., as unencrypted data). Therefore, any HTTP proxy component can intercept and modify header/data as it chooses—allowing custom data processing operations (including a custom compression operation) to be implemented. For HTTPS traffic, the data leaving a web-browser is encrypted. Therefore, a proxy cannot modify encrypted data, hence the novelty of the BPAHDP methodology. Both methods require specific implementation methods that are described. In particular, both embodiments of BPAHDP require specific techniques to facilitate the use of Microsoft Internet Explorer as a BPAHDP enabled web-browser. Microsoft COM (Component Object Model) interfaces and IE'"'"'s Pluggable Protocol capabilities are utilized to meet all requirements of both BPAHDP embodiments.

Claims

1. A method for custom processing HTTPS data, comprising the steps of:

a) creating a custom request header indicating that a web browser supports preselected customized processing operations;

b) sending the custom request header with a HTTP request over a secure communication channel to a web server;

c) receiving from the web server over the secure communication channel processed payload data and a HTTP response header correlatable therewith, wherein the processed payload data is created by processing original payload data based upon one or more of the customized processing operations supported by the web browser;

d) modifying the response header to create a modified response header;

e) modifying the processed payload data utilizing one or more of the customized processing operations to create modified payload data indicative of the original payload data; and

f) presenting the modified header and the modified payload data to the web browser.

2. The method of claim 1, also comprising the step of modifying a URL of an object to be fetched by the web browser over the secure communication channel.

3. The method of claim 2, wherein the object is a web site address for a content server.

4. The method of claim 1, wherein the secure communication channel is a Secure Socket Layer (SSC) connection or Transport Layer Security (TLC) connection.

5. The method of claim 1, wherein the web browser is a standard web browser

6. The method of claim 1, wherein the customized processing operations comprise, or are selected from the group comprising:

a compression operation, a decompression operation, an encryption operation, and a decryption operation.

7. A method for customized processing of HTTPS data, comprising the steps of:

a) sending a custom request header with a HTTP request over a secure communication channel to a web wherein the custom request header indicates that the web browser supports customized processing operations;

b) receiving from the web server over the secure communication channel processed payload data and a HTTP response header correlatable therewith, wherein the processed payload data is created by processing original payload data based upon one or more of the customized processing operations supported by the web browser; and

c) modifying the processed payload data utilizing one or more of the customized processing operations to create modified payload data indicative of the original payload data.

8. The method of claim 7, also comprising the step of modifying a URL of an object to be fetched by the web browser over the secure communication channel.

9. The method of claim 7, wherein the secure communication channel is a Secure Socket Layer (SSL) connection or a Transport Layer Security (TLS) connection.

10. The method of claim 7, wherein the customized processing operations comprise, or are selected from the group comprising:

a compression operation, a decompression operation, an encryption operation, and a decryption operation.

11. A web browser enabled for customized processing of HTTPS data, comprising means for performing the steps of:

a) creating a custom request header indicating that the web browser supports preselected customized processing operations;

b) sending the custom request header with a HTTP request over a secure communication channel to a web server;

c) receiving from the web server over the secure communication channel processed payload data and a HTTP response header correlatable therewith, wherein the processed payload data is created by processing original payload data based upon one or more of the customized processing operations supported by the web browser; and

d) modifying the processed payload data utilizing one or more of the customized processing operations to create modified payload data indicative of the original payload data.

12. The method of claim 11, also comprising means for modifying a URL of an object to be fetched by the web browser over the secure communication channel.

13. The web browser of claim 11, wherein the secure communication channel is a Secure Socket Layer (SSL) connection or a Transport Layer Security (TLS) connection.

14. The web browser of claim 11, wherein customized processing operations comprise, or are selected from the group comprising:

a compression operation, a decompression operation, an encryption operation, and a decryption operation.

15. A web browser plug-in for enabling a web browser to undertake the customized processing of HTTPS data, comprising means for modifying the web browser to perform the steps of:

a) modifying an outgoing request header to create a custom request header indicating that the web browser supports preselected customized processing operations;

b) sending the custom request header with a HTTP request over a secure communication channel to a web server;

c) receiving from the web server over the secure communication channel processed payload data and a HTTP response header correlatable therewith, wherein the processed payload data is created by processing original payload data utilizing one or more of the customized processing operations supported by the web browser;

d) modifying the response header to create a modified response header;

e) modifying the processed payload data utilizing one or more of the customized processing operations to create modified payload data indicative of the original payload data; and

f) presenting the modified header and the modified payload data to the web browser.

16. The web browser plug-in of claim 15, wherein the secure communication channel is a Secure Socket Layer (SSL) connection or a Transport Layer Security (TLS) connection.

17. The web browser plug-in of claim 15, wherein the web browser is Internet Explorer.

18. The web browser plug-in of claim 15, wherein the customized processing operations comprise, or are selected from the group comprising:

a compression operation, a decompression operation, an encryption operation, and a decryption operation.

19. A computer program product for use on a computer system for customized, processing of HTTPS data, the computer program product comprising:

a recording medium for recording means for instructing the computer system to perform the steps of;

a) creating a custom request header indicating that a web browser supports preselected customized processing operations;

b) sending the custom request header with a HTTP request over a secure communication channel to a web server;

c) receiving from the web server over the secure communication channel processed payload data and a HTTP response header correlatable therewith, wherein the processed payload data is created by processing original payload data based upon one or more of the customized processing operations supported by the web browser;

d) modifying the response header to create a modified response header;

e) modifying the processed payload data utilizing one or more of the customized processing operations to create modified payload data indicative of the original payload data;

f) presenting the modified header and the modified payload data to the web browser.

20. The computer program product of claim 19, wherein the computer program product is a web browser plug-in.