Hi bob3160,
Thanks for your comment. I hope DavidR could come up with some similar opinion of this extension and why he would not use it.
Damian
This could be a real pain in the backside blocking http content unless you specifically allow it. So it is forcing the user down the https route, by whatever means (probably having to use http everywhere) otherwise the user would be blocked from lots of site, a pain.
I don't know if this may also give the user lots of mixed content errors seen many times in these forums.
I don't think that forcing https (or blocking http) makes you any safer, so it means your traffic is encrypted, but that doesn't mean safer. You all know my feelings about that as currently it means that the web shield can't protect you. Just because a connection is https doesn't mean you can't get infected, just the reverse as you lose some of the avast protection.
####Now I know avast are looking at ways to be able to have https traffic scanned, not just http. When this comes to fruition, then forcing https isn't such an issue.
But even then this add-on would be a pain in the backside, a little like some feel about NoScript but much more severe as it would be blocking http, crazy.