diff options
| author | shess@chromium.org <shess@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-03-23 23:40:06 +0000 |
|---|---|---|
| committer | shess@chromium.org <shess@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-03-23 23:40:06 +0000 |
| commit | 83bfadc8f00117e0203dfc543c6f72e59d2aee96 (patch) | |
| tree | 25e25273b0f7d8a903251bee4193cae05fd20270 | |
| parent | c8abcd37be9e3ea1c342096b1729869ebc951a02 (diff) | |
| download | chromium_src-83bfadc8f00117e0203dfc543c6f72e59d2aee96.zip chromium_src-83bfadc8f00117e0203dfc543c6f72e59d2aee96.tar.gz chromium_src-83bfadc8f00117e0203dfc543c6f72e59d2aee96.tar.bz2 | |
Stats about safe-browsing update request size.
Large update requests can cause the server to return an error code.
Since the database is not udpated, this state is probably persistent.
Generate some stats to help decide whether to automate deletion of
such databases.
BUG=120219
Review URL: https://chromiumcodereview.appspot.com/12665009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@190118 0039d316-1c4b-4281-b951-d872f2087c98
| -rw-r--r-- | chrome/browser/safe_browsing/protocol_manager.cc | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/chrome/browser/safe_browsing/protocol_manager.cc b/chrome/browser/safe_browsing/protocol_manager.cc index 8ba91ca..437b41c 100644 --- a/chrome/browser/safe_browsing/protocol_manager.cc +++ b/chrome/browser/safe_browsing/protocol_manager.cc @@ -618,6 +618,11 @@ void SafeBrowsingProtocolManager::OnGetChunksComplete( update_list_data_.append(FormatList( SBListChunkRanges(safe_browsing_util::kMalwareList))); + // Large requests are (probably) a sign of database corruption. + // Record stats to inform decisions about whether to automate + // deletion of such databases. http://crbug.com/120219 + UMA_HISTOGRAM_COUNTS("SB2.UpdateRequestSize", update_list_data_.size()); + GURL update_url = UpdateUrl(); request_.reset(net::URLFetcher::Create( url_fetcher_id_++, update_url, net::URLFetcher::POST, this)); |