Rules for blocking web addresses in Web access protection

Discussion in 'ESET Smart Security v4 Beta Forum' started by userNamed, Jan 3, 2009.

Thread Status:
Not open for further replies.
  1. userNamed

    userNamed Registered Member

    Joined:
    Dec 29, 2008
    Posts:
    13
    I think the rules in the Blocked HTTP/HTTPS addresses list are poorly defined.

    For example, I cannot block a web address on a particular protocol. The use case here is for example my email provider Runbox. I only want to access it from HTTPS, so to protect me from myself I would like to block http:*.runbox.*. This does not work. Try adding it to the list and you will see what I mean.

    There is also a problem with double slash. Adding any address with a double slash // (such as one with a protocol http:// or web.com//document) will result in a really bad rule called * (blocks every address). :ouch:

    Trailing slashes is another big problem. I want to block *.somesite.com/ads/* but the rule gets changed to *.somesite.com/ads*, which also blocks *.somesite.com/adsomethingofvalue. This is actually a more and more frequent problem for me.

    *urchin*.js* is a rule that targets Google Analytics. It is, however, ignored. :mad: (There are quite a few variations of this file name in use. The thnigs they all have in common is that they are .js files and the name either starts or ends with urchin.)

    There are other problems as well, but these were the ones I could remember right now. I hope the content clocker is improved for the final release.
     
Thread Status:
Not open for further replies.