Transparent mode: In transparent mode, all connections made by client browser applications on port 80 (port 443, respectively, if SSL is used) are intercepted and redirected to the Web Filter without client-side configuration. The client is entirely unaware of the Web Filter server. The advantage of this mode is that no additional administration or client-side configuration is necessary, the disadvantage however is that only HTTP (port 80) requests can be processed. Thus, when you select the transparent mode, the client's proxy settings will become ineffective.
So, now, what I don't get, is, when I use the proxy in transparent mode, according to the helpfile article, requests on port 443 (https) are redirected to the web filter (proxy), but not processed ("the disadvantage however is that only HTTP (port 80) requests can be processed")?
If that is correct, does the checkbox "Scan HTTPS (SSL) traffic." has any effect on that behavior in this mode or only in standard mode?
So is it somehow possible to scan https traffic in transparent mode or just http traffic and allow https with a firewall rule?
Next thing is, if I want to scan https traffic, I need a valid SSL certificat that the clients will accept or import the self signed certificat from the UTM in the clients browser, right? Otherwise an untrusted SSL certificat message will pop up I guess.
Thanks for your info, Albeck.
This thread was automatically locked due to age.
