Hi true indian,
You really consider that after the "Firesheep" extension with the HTTPS Connection Flaw drama in Febr. last year? Just think again.
You need the full shield detection of avast on normal http connections allways.
With https you loose that additional protection.
I know our forum friend, DavidR, did advise against this forcing of HTTPS-connections on several occasions and in several of his postings. I have to agree with his opinion.. Not all browsers will tell you when https is in part insecure, and not all browsers then block the insecure javascript.
re:
http://techie-buzz.com/browsers/google-chrome-blocks-insecure-scripts.html (link article author = Keith Dsouza)
I would not like to run the additional risks, but that is just my personal opinion,
I would install the Ghostery plug-in with all the new total blocking options and enable bug blocking there, re:
http://www.ghostery.com/ polonus