HTTPS scan not working in Vivaldi web browser

Hi, I’m using Avast Free Antivirus 17.2.2288 (build 17.2.3419.0) and I think the web shield doesn’t scan HTTPS traffic when using Vivaldi web browser (free software based on Chrome).

I’m on Windows 10 x64 Anniversary Update (version 1607 compilation 14393.693) with EMET installed and configured for all web browsers.
I’ve also tested this on Windows 7 without EMET and got same results.

To test this I’ve tried downloading eicar test file.
When using Vivaldi (1.7.735.46 (Stable channel) (32-bit)) the files get blocked if downloaded by HTTP, but gets saved to disc if downloaded over HTTPS connection.

To further test this I’ve used Google Chrome (56.0.2924.86 (64-bit)).
In Chrome the eicar test file gets blocked when downloaded over both HTTP and HTTPS.

The problems seems to be Avast not scanning HTTPS traffic specifically in Vivaldi web browser, but working for other browsers.
This is a major issue for me, since HTTPS connections are used by majority of the sites I visit.

Any help resolving this will be appreciated.

Vivaldi is not based on Chrome, but is using the Chromium engine. :wink:

Yes, it’s based on Blink, same as Chrome.
My point was more that it should be similar to Chrome internally and Avast works with Chrome :wink:

As a side note, the HTTPS scanning did work for Vivaldi in Avast 2016.

It’s working for me, and I’m a Vivaldi user.
Try a repair…Control Panel>Programs and Features>Uninstall a Program>double click “avast”>click “repair”>reboot.

The eicar test file is not for testing https scanning.

Thanks for your help.
I’ve tried the repair options, but it didn’t solve my issue.
Strange you cannot reproduce it on your system, might be some peculiarity of my system configuration.

Why?
I mean, it’s a harmless file that’s detected as a virus, which sounds like a perfect test to me.
Especially since the file is detected on one browser I’ve installed, but not on the other.

http://www.eicar.org/86-0-Intended-use.html
http://www.eicar.org/85-0-Download.html

I’ve read it before using the file.

I think I fall into the third group of users (highlight added by me):

A third set of requests come from exactly the people you might think would be least likely to want viruses "users of anti-virus software". [b]They want some way of checking that they have deployed their software correctly[/b], or of deliberately generating a "virus incident in order to test their corporate procedures, or of showing others in the organisation what they would see if they were hit by a virus".
I think they provide both HTTP and HTTPS links for a reason.