How to block https://www.yousite.com ????

[sithisak]

Hello, Forum ^_^

I testing avast 6 free version and in Site Blocking Feature i found it can't block https:// protocal
ex. https://www.facebook.com or https://www.twitter.com (i want to block my children to access site)

Type site in list same this image and go to browser. Type https:// avast can't block site because
in list read it http://https://www.facebook.com. How to fix it?

Thank you, Avast Team

[DavidR]

I don't know why it adds the http, one possibility is that since this relates to the web shield and the web shield doesn't monitor https traffic (it can't secure, encrypted) so it may think it should have http in front.

However you are making life difficult for yourself as  *facebook.com/* should cater for all of those instances http://facebook.com www.facebook.com or https://facebook.com.

OK I tested that mask and it works for the first two, but not for the https connection because as I suspected the URL Blocking uses the web shield to achieve this blocking and as stated the web shield doesn't monitor https traffic.

So you could try blocking this in your firewall or in your HOSTS file.

[sithisak]

Thank you for trick work right now

Cheer up! Avast  

[SpeedyPC]

And make sure you set up a password for you're Avast settings so the kids cannot take and control you're Avast settings to remove the block site feature set up

So you could try blocking this in your firewall or in your HOSTS file.

+1 I agree with DavidR

[akshayk29]

Thank you for trick work right now

Cheer up! Avast  

you are blocking http://ads* , does it block all ads?

[DavidR]

Thank you for trick work right now
<snip>

You're welcome.

However, you should use the mask that I showed *facebook.com/* note the / after the com and before the *. This ensures that it is actually facebook that is blocked and not a facebook sub-domain of a different site, for example facebook.comcast.com I don't know if this is a legit name (just an example).

There must be tens/hundreds of thousands of domain names beginning with com and they might have a sub-domain relating to facebook, but isn't actually facebook.com. So I try to be careful in the use of URL masks as they can have unforeseen circumstances.

[DavidR]

Thank you for trick work right now

<snip>

you are blocking http://ads* , does it block all ads?

@ akshayk29
Please modify your post (button to the right of your post), and remove the image link as I did in my post and in your quoted text, there is no need to repeat the image every time of the topic gets very long.

However in answer to your question, the answer is NO as there are too many permutations for ads URLs. This URL mask is poorly constructed, not likely to be very effective/efficient and is likely to trap sites that have nothing to do with adverts, those with domain names beginning with ads.

Ads blocking is a specialist task and for that most browsers have ad blocking built in or you can use an extension, AdBlock Plus for firefox. Or use a HOSTS file manager they are much better at this sort of thing.

[YoKenny]

Or use a HOSTS file manager they are much better at this sort of thing.

+1

[sithisak]

Thank you for trick work right now

Cheer up! Avast  

you are blocking http://ads* , does it block all ads?

Yep, is work block in word " ads " all link.

[danny96]

hehe It works! I typed in ad and now it blocks everything that contains ad, so ad.youtube.com blocked

[akshayk29]

hehe It works! I typed in ad and now it blocks everything that contains ad, so ad.youtube.com blocked

add these and now all your ads are blocked!!!
http://ads*
http://ad*

[DavidR]

If you think that all internet ads delivery functions all start with this string (if only it were so easy), I'm afraid you are in for a surprise, there really are better tools out there.

There is also no need for the first mask if you have the second one, as that covers that catered for by the first.

See images, which is a very small sample of the lists in adblock+ for firefox. The first image whilst it has ad in the first two characters, there is no guarantee that it will be proceeded with http :// So if that happens your mask won't work and putting a wildcard in place of the http :// would make it too general and trap many legitimate sites.

The second image shows just a few that don't even have add in the string at all.

[akshayk29]

one thing i hate about adblockers is that they are not available to chrome!!

[DavidR]

That is hardly the adblockers fault.

Chrome has taken a long time to start to build up extension support (that is what stopped me using Chrome), but now there is a reasonable level of support I would check again and see if there are any now.

[akshayk29]

that's why chrome is not no.1 in browser wars