Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(6111)

Unified Diff: chrome/browser/safe_browsing/client_side_detection_service.h

Issue 7408001: If we show a SafeBrowsing warning we always send the client-side detection (Closed) Base URL: http://git.chromium.org/git/chromium.git@trunk
Patch Set: Merge Created 9 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: chrome/browser/safe_browsing/client_side_detection_service.h
diff --git a/chrome/browser/safe_browsing/client_side_detection_service.h b/chrome/browser/safe_browsing/client_side_detection_service.h
index f9d1c8bf42025a91c3a792685a7c0a5b2dc235f9..3fb5e496a13b0f165ab100cfb66b70a6f6c64299 100644
--- a/chrome/browser/safe_browsing/client_side_detection_service.h
+++ b/chrome/browser/safe_browsing/client_side_detection_service.h
@@ -85,7 +85,8 @@ class ClientSideDetectionService : public URLFetcher::Delegate,
// occurs during the fetch. If an error occurs the phishing verdict will
// always be false. The callback is always called after
// SendClientReportPhishingRequest() returns and on the same thread as
- // SendClientReportPhishingRequest() was called.
+ // SendClientReportPhishingRequest() was called. You may set |callback| to
+ // NULL if you don't care about the server verdict.
virtual void SendClientReportPhishingRequest(
ClientPhishingRequest* verdict,
ClientReportPhishingRequestCallback* callback);

Powered by Google App Engine
This is Rietveld 408576698