The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.

The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.

Date of Patent:
Dec. 29, 2015

Filed:

Oct. 28, 2009
Applicants:

Akshay Nanduri, Waterloo, CA;

Ajit Singh, Waterloo, CA;

Salmaan Ahmed, Waterloo, CA;

David Sze, Kitchener, CA;

Inventors:

Akshay Nanduri, Waterloo, CA;

Ajit Singh, Waterloo, CA;

Salmaan Ahmed, Waterloo, CA;

David Sze, Kitchener, CA;

Assignee:

SLIPSTREAM DATA INC., Waterloo, CA;

Attorneys:
Primary Examiner:
Int. Cl.
CPC ...
G06F 15/173 (2006.01); H04L 29/06 (2006.01); H04L 29/08 (2006.01);
U.S. Cl.
CPC ...
H04L 69/04 (2013.01); H04L 63/166 (2013.01); H04L 67/02 (2013.01);
Abstract

The invention described here deals with implementing custom data processing of HTTPS based on a Browser-Plugin Method. Such 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.


Find Patent Forward Citations

Loading…