adrien wrote:WinGate 7's HTTP proxy has the capability to intercept on port 443 to a binding using SSL, and it then makes a SSL connection to the server. At the moment we don't spoof certificates although this is on the cards. What that means is if you decide to intercept port 443 in WinGate 7 to a WWW proxy using SSL on its bindings, then it will work but give certificate nag warnings to the users (most users just click ok anyway).
Thank you for the information. Do you expect or meet that some applications could fail to work properly in the case of such a double SSL connections?
logan wrote:You can still block HTTPS access by the server name (e.g.
http://www.server.com), but the path (everything after the server name) is encrypted and we can't do anything with that. I should also mention that you can only do this if the client is manually configured to use the proxy server.
Several month ago I had an issue with
www.toto.am website. Wait, need to remember and check.
...
I just checked, it was not Wingate issue, but PureSight. I had gambling denied in PS, but was asked by the chief to allow the site for 10 minutes. After enabling the restriction again I found that users are still able to connect to the site by https.
I realise now, the problem is PS is not checking sites accessed by https at all! Very sad and wrong. Can you influence somehow on the developer?
P.S. Just checked, indeed Wingate is able to block the website by url contents. Very good.