Switch to full style
Forum for support for the PureSight for WinGate content filtering plugin
Post a reply

PureSight don't block HTTPs Sites

Sep 26 14 9:39 pm

Hi,

just setup my WinGate 8 with a 30 Trial PS. All works as expected.
I configured to block "Social Networking" and "http://www.facebook.com" will be blocked - fine.
But if i load https://www.facebook.com, the Site would be load normally - are there any solutions for this problem ?

Re: PureSight don't block HTTPs Sites

Oct 10 14 8:12 pm

Hi,

I get the same issue, if we put some sub domain of facebook such as: *.facebook.com, then the access fules didn't ban.

It seems that PureSight didn't get good database and it does not work correctly as expecting.

Tai

Re: PureSight don't block HTTPs Sites

Oct 22 14 8:49 am

https can be quite different (in terms of blocking) than http. It depends on how your client browsers are configured.

It sounds like probably the clients are not configured to use a proxy, and so https access is going over NAT and not via the WWW proxy. In this case https won't be filtered by the web access rules etc since it's not going through the web proxy. To get around this, you'll need to configure the clients to use a proxy.

If you're on an Active Directory you can use a GPO to set proxy.

Re: PureSight don't block HTTPs Sites

Oct 22 14 8:50 am

taihoang wrote:Hi,

I get the same issue, if we put some sub domain of facebook such as: *.facebook.com, then the access fules didn't ban.

It seems that PureSight didn't get good database and it does not work correctly as expecting.

Tai


Where did you put the sub-domains of facebook? E.g. is it in a Data list, or a file, or in a web access rule, or in a manual classifier rule?
Post a reply