by Pascal » Oct 04 04 11:43 pm
I'll need to check the code (At home at the moment). It is possible that the list checking might be done before we make a determination about which plugins to apply (Based on the protocol) but I believe none of the plugins will function on HTTPS traffic, simply because none can understand the traffic. (It's all encrypted).
As PureSight is primarily designed as a content filter it not being able to understand HTTPs (Even if we passed it through) would not give you any additional benefit. The client side browser can decode it because it's negotiated the session keys with the server, etc. (WinGate, as a man in the middle, cannot understand that encrypted traffic)
The ban list in WinGate, along with policies, cover that situation. They are a bit tricky to setup, but give you that bannable functionality.