diff options
| author | cevans@chromium.org <cevans@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-03-24 03:37:40 +0000 |
|---|---|---|
| committer | cevans@chromium.org <cevans@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-03-24 03:37:40 +0000 |
| commit | b9cedd2c447e11a52f09e6265820a47964f38c19 (patch) | |
| tree | fde6c2649839aee438eed89f2b7d8565e85952c5 /chrome | |
| parent | 96acaec29e9db6d6fda52af2ce2d96abf5294727 (diff) | |
| download | chromium_src-b9cedd2c447e11a52f09e6265820a47964f38c19.zip chromium_src-b9cedd2c447e11a52f09e6265820a47964f38c19.tar.gz chromium_src-b9cedd2c447e11a52f09e6265820a47964f38c19.tar.bz2 | |
Up the safe browsing timeout from 1s to 5s.
After a conversation with Eric, we're not worried about attacker pages loading
down the local machine or network (because such pages would themselves be
candidates for being flagged).
The concern is users with slow network connections, or random network / server
jitter.
BUG=36774
TEST=NONE
Review URL: http://codereview.chromium.org/1242001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42425 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome')
| -rw-r--r-- | chrome/browser/renderer_host/safe_browsing_resource_handler.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/chrome/browser/renderer_host/safe_browsing_resource_handler.cc b/chrome/browser/renderer_host/safe_browsing_resource_handler.cc index f8691f0..cf5ed3e 100644 --- a/chrome/browser/renderer_host/safe_browsing_resource_handler.cc +++ b/chrome/browser/renderer_host/safe_browsing_resource_handler.cc @@ -14,7 +14,7 @@ // Maximum time in milliseconds to wait for the safe browsing service to // verify a URL. After this amount of time the outstanding check will be // aborted, and the URL will be treated as if it were safe. -static const int kCheckUrlTimeoutMs = 1000; +static const int kCheckUrlTimeoutMs = 5000; // TODO(eroman): Downgrade these CHECK()s to DCHECKs once there is more // unit test coverage. |