I just installed avast after using bitdefender free for a long time. But avast blocks random wiki images, often gif. When I followed link, it showed this
ERR_SPDY_PROTOCOL_ERROR
It worked shortly after change DNS, but then the problem reappeared. It seems the DNS is not the source of the problem. Googled it and it seems some people got it too with avast and chrome
I’m having exactly the same issue on a different website. Interestingly, the problem for me is also happens with gif files (it happened once for png files too). Everything else is fine on the same domain, but the gifs are never.
I have tried on a clean installed Windows 10 and on a Windows 8.1 and it’s always happens but only with Google Chrome.
The error is always the same too: ERR_SPDY_PROTOCOL_ERROR
I have also tried turning off the https scanning, but the result was the same. As soon as I disable the web shield feature, it works. After I re-enable it, it works for X hours, then the problem starts again. It started like a month or two ago. I’m using the latest avast Premier version (10.3.2225). I think it started with an earlier update.
Edit: A few plus info. I don’t have comodo firewall, I use Google DNS too, but it’s managed by the router, the PC gets the router’s IP as a DNS server via DHCP.
I have also tried to play with the settings, but the only solution is to turn off the web shield component.
I have also read and experienced an issue on normal a normal webpage: the error showed up, then page refreshed (google chrome tries to load the content again if there is an issue), and the page loaded fine.
Edit 2: The issue is also represent on facebook for example. Again, the gifs…
Is there anyone from Avast who can help me/I can help him to debug this?
Once I load it the first time, it usually displays all .gif images like it should, but if I refresh page once all those images disappear and refuse to load. However, if I do a complete reload (CTRL+F5), they display again. Other sites don’t display the same behavior, which is quite strange.
E: Also the problem is certainly caused by avast, as disabling Web Shield fixes the problem instantly. On the other computer using Avast Free adding .gif files to web shield exclusion list fixed all problems, but on the other computer using Avast Pro Antivirus it doesn’t change a thing.
E2: apparently disabling HTTPS scanning fixes it for the computer using Pro AV too, still really strange bug that devs should look into.
With Firefox 40.0.3, the only image that doesn’t reload on a refresh for me is the first animated .gif, the others are there.
Shift + F5 or Shift + refresh icon restores it.
I don’t know why it would exhibit this behaviour for animated gifs.
Ah, sorry for forgetting that info. It happens with both Firefox 40.0.3 and Chrome 44.0.2403.157. Clearly it has something to do with HTTPS scanning, as disabling it removes the problem instantly.
It is hard to say, if there is a conflict of any sort, removing one element may resolve a problem but it doesn’t say for sure what is the true culprit.
Since the page is HTTPS, with the web shield not scanning it you aren’t going to get the interaction.
I’m having an issue with the Yahoo home page not loading any images. If I turn off the shields the images load. Turn the shields back on and the images fail to load. I’m using Firefox 40.0.3 and Avast Free 10.3.2225 on Win 7. This just started yesterday. Any suggestions?
Did you happen to update yesterday (or just use yahoo home page that day) as it would be strange if it had previously worked with this build/version.
Don’t turn of the shields, disable HTTPS scanning (avastUI > Settings > Active Protection > Web Shield > Customize - disable HTTPS scanning. That is a minimal action rather than completely disabling shields.
Didn’t update yesterday. Last update was about 4 weeks ago. I use Yahoo home page daily. It worked until yesterday. I disabled HTTPS scanning and all the images load. When I turn it back on they don’t load. Makes no sense why it would do this all of a sudden.
Exactly as I said, weird that it would be working. I hadn’t previously had a problem, but I’m on the latest beta builds and since then I have had the issue.
That would be different as I don’t know exactly what had changed. I was OK on the 2228 beta build, but I ended up with a build that shouldn’t have been installed on XP and that is I suspect where my problem came from.