I’ve faced with that the site blocking feature of AIS does not accept https (only http).
I’ve tried the * but the site is not blocked.
Is there a limit to block the https content?
Why does the site block feature appear into the passworded ones (it could work as a limited parental control)?
Is it that difficult to implement? Could you?
I believe (Lukor might correct me) that the site-blocking feature is internally still part of the WebShield… therefore no https.
well that’s interesting, as as far as I remember, when people (not me) complained that site blocking that was part of the web shield in the free version of Avast 4 wasn’t part of Avast 5 “free” anymore, the answer from Avast was that the “site blocking” feature was a firewall feature, therefore couldn’t belong anymore to the free version but would be from now on an AIS feature 8)
ps: meaning that technically, the webshield does the job, but commercially, only AIS does ;D
edit: I do agree that site blocking is a firewall-like feature, but it’s always been obvious to me that it doesn’t need a firewall to run 
Well, as I said, I’m not completely sure about it - and even if it is this way now, it might change in future versions (IMHO it would make more sense for the firewall to do that, as it could block anything).
good that you posted that (not your last post, but the one before), because I just checked (never did as I don’t use the feature) >>> blocking a site generates an entry in the webshield.ini file. So yeah, the WS is indeed still taking care of that 
entry looks like that:
URLBlocking=1
BlockedURLs=http://www.xxxxxxx.com*
can’t try right now 'cause I got AIS, but I’m wondering what would happen if the entry was manually added in the “free” version ??? 
well it needs activation of the feature (urlblocking=1), so it may not work.
Exactly what was said before…
Strange that it is managed by Web Shield yet. It’s a firewall job.
Lukas?