Add API keys to SafeBrowsing client-side phishing and download verdict requests.

Add API keys to SafeBrowsing client-side phishing and download verdict requests.


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=156755

[mattm, 2012-09-14 03:21:52]

On 2012/09/14 00:15:05, Brian Ryner wrote:

Can you try both of these CLs locally with safe_browsing_tests? (use
--gtest_also_run_disabled_tests)

[Brian Ryner, 2012-09-14 03:52:58]

Good call.  This one is fine, but http://codereview.chromium.org/10914274/
fails.  It needs a small tweak to safebrowsing_test_server.py to ignore the new
parameter.  I'll commit that upstream and include a DEPS roll.

On 2012/09/14 03:21:52, mattm wrote:
> On 2012/09/14 00:15:05, Brian Ryner wrote:
> 
> Can you try both of these CLs locally with safe_browsing_tests? (use
> --gtest_also_run_disabled_tests)

[mattm, 2012-09-14 04:17:30]

lgtm

[commit-bot: I haz the power, 2012-09-14 04:22:56]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/bryner@chromium.org/10907225/1

[commit-bot: I haz the power, 2012-09-14 06:12:07]

Commit queue rejected this change because the description was changed
between the time the change entered the commit queue and the time it
was ready to commit. You can safely check the commit box again.

[commit-bot: I haz the power, 2012-09-14 06:31:09]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/bryner@chromium.org/10907225/1

[commit-bot: I haz the power, 2012-09-14 06:31:21]

Change committed as 156755