Reference Guide
...
HTTP Proxy
HTTP Proxy SSL/TLS Mode
2 min
secure http (https) is already supported in single connect configurations are the same for both http and https all http requests, responses, headers, and contents sent and received during the session are logged indisputably although single connect secures all communication after authentication through https protocol, authentication is performed through the http protocol by default on the web browser; this information can be obtained if the network is captured to eliminate this risk, the http proxy can be configured to use the https protocol, even for proxy authentication to enable ssl on the http proxy, the http proxy ssl enabled parameter should be set as true and the http proxy protocol parameter should be changed from http to https these parameters are located under /u01/http proxy/conf/http proxy properties this property is used together with the http proxy host parameter meaning that if the http proxy ssl enabled parameter is set to true, the http proxy generates a certificate at runtime containing the given host as the subject alternative name to ensure it is trusted by the browser otherwise, the browser will reject requests therefore, to configure http proxy settings on the browser or os, the http proxy host parameter must be the same as the given host/ip to use this feature, the web browser must be started with the https protocol for authentication for the chrome instance, it must be started as follows in the end user browser to start the session with ssl chrome proxy server=https //http proxy host 7080 as shown in the chrome browser example, end users must open other browsers differently since this feature affects the end user experience, it must be configured carefully http proxy in ssl/tls mode usage with single connect desktop client when reaching http proxy which operates at ssl/tls mode from the desktop client, the use ssl must be checked under the http proxy tab in the single connect desktop client