Getting warning: FIle is not commonly downloaded and could be dangerous
Reported by
harsh.ma...@gmail.com,
Apr 10 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36 Steps to reproduce the problem: 1. Go to http://harshmaurya.in/vector-to-wpf-xaml-converter/ 2. Click on download 3. Chrome will show a warning after the download completes What is the expected behavior? It should not show the warning What went wrong? I am getting this warning for all the zip files in my website. All the files are completely safe and are virus/malware free. Not sure why it is being shown as a warning. This is not good for my business. Did this work before? N/A Chrome version: 49.0.2623.110 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 21.0 r0
,
Apr 10 2016
,
Apr 10 2016
No this does not happen in Edge.
,
Apr 10 2016
,
Apr 10 2016
This is WAI. Once Google's Safe Browsing has scanned these files it can properly classify it as safe or unsafe. Until then, new archives with potentially dangerous files as contents will be marked as "uncommon downloads."
,
Apr 11 2016
This is not "Working As Intended". The same files when archived into a .rar doesn't trigger the warning whereas it triggers for .zip nparker's reply is based on just wild guess without any actual analysis. @Others: There are many different reasons for the issue from what I have researched. Some solution may work for you while some may not.
,
Apr 11 2016
There is an explanation for the behavior you're seeing: Chrome unpacks .zips to look for dangerous file types. If it sees one, it will ask Google Safe Browsing about them and get a verdict. Sometimes that verdict is "uncommon," hence the warning. Chrome doesn't not currently unpack .rar files, so they are opaque to Chrome. Chrome _will_ ask Safe Browsing about the .rar file, but if the archive hasn't been seen/unpacked by Google Safe Browsing, then the default behaviour is to call it "safe."
,
Apr 11 2016
Thanks for clearing it up. This will be helpful for others as well. Seems like this is a very common problem. Chrome should not flag the uncommon files by default, it is not good for small developers/business.
,
Apr 11 2016
+auk for visibility. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by wfh@chromium.org
, Apr 10 2016