summaryrefslogtreecommitdiffstats
path: root/chrome/browser/safe_browsing/client_side_detection_service_unittest.cc
Commit message (Expand)AuthorAgeFilesLines
* Remove the check of the whitelist entries in ClientPhishingResponse.bryner@chromium.org2011-12-081-43/+2
* Convert to base::Callback in safe_browsing client-side-detection code.shess@chromium.org2011-11-231-1/+3
* Move BrowserThread to content namespace.joi@chromium.org2011-11-021-0/+1
* Split BrowserThread into public API and private implementation, step 1.joi@chromium.org2011-10-281-5/+7
* Rename URLFetcher to be URLFetcherImpl, now that we have the content::URLFetc...jam@chromium.org2011-10-271-1/+0
* Only send the client-side phishing model to a renderer if its profile has Saf...bryner@chromium.org2011-10-191-11/+11
* Include the URL and all features in the CSD pingback for all users.bryner@chromium.org2011-10-161-89/+0
* Change browser features to use redirect chain for redirects tracking.gcasto@chromium.org2011-10-081-6/+6
* Convert SHA256_LENGTH from a constant-in-anonymous-enum to a static const. T...pkasting@chromium.org2011-09-221-10/+10
* Switch to the new client-side phishing model that uses Murmurhash for word ha...bryner@chromium.org2011-09-131-8/+0
* Move URLFetcher from content/common to content/common/net.willchan@chromium.org2011-09-131-1/+1
* Fix Linux Views build breakage.willchan@chromium.org2011-09-131-1/+1
* Move URLFetcher from content/common to content/common/net.willchan@chromium.org2011-09-131-1/+1
* Parse the whitelist expressions from the phishing verdict response ifnoelutz@google.com2011-08-311-3/+43
* Change the client-side phishing detection hashing function tonoelutz@google.com2011-08-301-4/+3
* Switch ChromeTestSuite to the same convention as ContentTestSuite:phajdan.jr@chromium.org2011-08-271-2/+1
* Add support for client-side phishing detection for non-UMA users.bryner@chromium.org2011-08-261-0/+105
* Revert 98168, it caused compile errors on mac:thakis@chromium.org2011-08-251-105/+0
* Add support for client-side phishing detection for non-UMA users.bryner@chromium.org2011-08-251-0/+105
* Add "enabled" state to the ClientSideDetectionService.joaodasilva@chromium.org2011-08-231-0/+87
* Reorganize chrome/test, part #9phajdan.jr@chromium.org2011-08-111-1/+1
* Check that all the hashes ids in the model are valid.noelutz@google.com2011-08-041-0/+58
* GTTF: Use a fresh TestingBrowserProcess for each test, part #4phajdan.jr@chromium.org2011-08-031-1/+2
* Add a scoper object for URLFetcher::Factoryphajdan.jr@chromium.org2011-07-291-3/+1
* Remove obsolete cleanup code for old SafeBrowsing client-side models.bryner@chromium.org2011-07-281-20/+6
* Add a new BrowserFeature for client-side FakeAV detection that is setnoelutz@google.com2011-06-291-3/+142
* Initial CL to update the client model more frequently. This CL also changes ...noelutz@google.com2011-06-171-20/+121
* Revert 89098 - Initial CL to update the client model more frequently.rsesek@chromium.org2011-06-161-120/+0
* Initial CL to update the client model more frequently.noelutz@google.com2011-06-141-0/+120
* Move UrlFetcher to content. I originally thought that it's only used by chro...jam@chromium.org2011-06-011-2/+2
* Move scoped_temp_dir and scoped_native_library back from base/memory to base.thakis@chromium.org2011-05-191-1/+1
* Remove safe_browsing code from BrowserRenderProcessHost. Also remove crash r...jam@chromium.org2011-05-021-47/+0
* Change the client-side phishing detection request format. Instead ofnoelutz@google.com2011-04-141-5/+8
* Move some files from base to base/memory.levin@chromium.org2011-03-281-3/+3
* Move cache and report checking to before classification is run.gcasto@chromium.org2011-03-141-47/+16
* Don't run the phishing classifier if the page was loaded from a private IP ad...bryner@chromium.org2011-03-021-74/+19
* Move files out of chrome\browser\renderer_host\test alongside their source. ...jam@chromium.org2011-02-241-3/+3
* Add caching to phishing client side detection.gcasto@chromium.org2011-02-141-6/+109
* Run pre-classification checks in the browser before starting client-side phis...bryner@chromium.org2011-02-111-0/+79
* Limit the number of requests sent by phishing client side detection per day.bryner@chromium.org2011-01-271-0/+42
* Remove thumbnails from the ClientSideDetectionService.bryner@chromium.org2011-01-141-17/+4
* Wait for all the pending tasks to be done before we tear down the client sidenoelutz@google.com2010-11-171-12/+19
* Disable ClientSideDetectionServiceTest.SendClientReportPhishingRequest on Macisherman@chromium.org2010-11-161-1/+8
* Fix Valgrind errors that occurred during testing.noelutz@google.com2010-11-151-0/+1
* Add a client-side phishing detection service class.noelutz@google.com2010-11-111-0/+183