Propagate the SafeBrowsing download protection verdict to the DownloadItem.

content/browser/download/download_state_info.h

Index: content/browser/download/download_state_info.h
diff --git a/content/browser/download/download_state_info.h b/content/browser/download/download_state_info.h
index 0729fe2089ef0208cc4a4372e2b9f3245b6c8f76..840dd860b02c0cc1cc58d38fa82babf89778128f 100644
--- a/content/browser/download/download_state_info.h
+++ b/content/browser/download/download_state_info.h
@@ -23,7 +23,9 @@ struct DownloadStateInfo {
                     bool prompt_user_for_save_location,
                     int uniquifier,
                     bool dangerous_file,
-                    bool dangerous_url);
+                    bool dangerous_url,
+                    bool dangerous_content,
+                    bool needs_quarantine_file);
 
   // Indicates if the download is dangerous.
   CONTENT_EXPORT bool IsDangerous() const;
@@ -56,6 +58,14 @@ struct DownloadStateInfo {
   // If safebrowsing believes this URL leads to malware.
   bool is_dangerous_url;
 
+  // If safebrowsing believes this content to be malicious.
+  bool is_dangerous_content;

[Randy Smith (Not in Mondays), 2011/11/16 17:52:41]

Any reason not to shift over to using an enum (maybe the standard enum?) for
these three?  The proliferation of bools is a bit disturbing.

[noelutz, 2011/11/16 23:15:07]

Done.

+
+  // True if the file is potentially dangerous.  If true, the download content
+  // will be written to a temporary file that isn't easily accessbile to the
+  // user.
+  bool needs_quarantine_file;

[Randy Smith (Not in Mondays), 2011/11/16 17:52:41]

I'd like to add this to the above enum, if we could (all the way into
DownloadItem is fine)--something like "MAYBE_DANGEROUS_CONTENT"?

[noelutz, 2011/11/16 23:15:07]

Done.

+
   // True if this download's file name was specified initially.
   FilePath force_file_name;
 };