Page 1 of 1

How to disable download prompt: "This type of file can harm"

Posted: Sat May 25, 2013 7:14 am
by pstein
When I download simple *.pdf files then always a prompt at the bottom of the browser appears:

"This type of file can harm your computer. Do you want to keep 0901732423b2345.pdf anyway?"

I always click here "Keep".

How can I tell Iron to suppress this type of prompt in the future?

Peter

Re: How to disable download prompt: "This type of file can h

Posted: Sat May 25, 2013 10:12 pm
by mapx
1. settings - advanced - privacy: try uncheck "Enable phishing and malware protection" and test again

or

2. settings - advanced - downloads - check "Ask where to save each file before downloading"

Re: How to disable download prompt: "This type of file can h

Posted: Sun May 26, 2013 6:03 am
by pstein
mapx wrote:1. settings - advanced - privacy: try uncheck "Enable phishing and malware protection" and test again

or

2. settings - advanced - downloads - check "Ask where to save each file before downloading"

Ok, thank you, BUT:

"Enable phishing and malware protection" is already unchecked.

and

"Ask where to save each file before downloading" ...-> I don't want to be asked.
Iron should AUTOMATICALLY store the download files in the directory just entered above this option in
settings - advanced - downloads


Any other ideas?

Re: How to disable download prompt: "This type of file can h

Posted: Sun May 26, 2013 3:24 pm
by mapx
it's a known "issue" in the chrome world ... there are no (other) solutions. Iron guys dont modify the chrome behaviour, they only remove some code to enhance privacy.

Re: How to disable download prompt: "This type of file can h

Posted: Mon Jul 29, 2013 4:46 pm
by robertcollier4
http://superuser.com/questions/594792/d ... -in-chrome
I fear that the only way to disable this is to patch Chrome.

The file that contains the blacklist is /src/chrome/browser/download/download_extensions.cc.

One would just need to remove the line containing { "pdf", AllowOnUserGesture }, and recompile.

Or replace DownloadDangerLevel GetFileDangerLevel(const base::FilePath& path) with:

DownloadDangerLevel GetFileDangerLevel(const base::FilePath& path) {
return NotDangerous;
}
which seems to have some irony to it.

UPDATE: I wrote a patch and have successfully tested it.

--- chromium-26.0.1410.43-old/chrome/browser/download/download_extensions.cc 2013-03-21 21:14:04.000000000 -0400
+++ chromium-26.0.1410.43-new/chrome/browser/download/download_extensions.cc 2013-06-04 11:51:40.000000000 -0400
@@ -213,6 +213,7 @@
};

DownloadDangerLevel GetFileDangerLevel(const base::FilePath& path) {
+ return NotDangerous;
base::FilePath::StringType extension(path.Extension());
if (extension.empty())
return NotDangerous;
If on Gentoo, you can just place this in a file in /etc/portage/patches/www-client/chromium/ and emerge chromium.