Fix the secure proxy check state displayed on net-internals#bandwidth.

Fix the secure proxy check state displayed on net-internals#bandwidth.

In the Data Reduction Proxy event store, if the secure proxy check failed
due to an HTTP response status failure, or a content failure (i.e. the
check returned text that wasn't "OK"), the net-internals#bandwidth page
would indicate that the secure proxy check (incorrectly) succeeded.

Other logs on the page would show the failure of the secure proxy check.

This is a logging/display only bug (no functionality was affected).

BUG=496731
Committed: https://crrev.com/3f0baabb34dd8b112b8da00cb94f206b6f7717db
Cr-Commit-Position: refs/heads/master@{#333017}

[jeremyim, 2015-06-04 16:45:22]

jeremyim@chromium.org changed reviewers:
+ sclittle@chromium.org

[jeremyim, 2015-06-04 16:45:23]

PTAL!

[sclittle, 2015-06-05 01:25:59]

LGTM % nit

https://codereview.chromium.org/1154623008/diff/1/components/data_reduction_p...
File
components/data_reduction_proxy/core/common/data_reduction_proxy_event_store_unittest.cc
(right):

https://codereview.chromium.org/1154623008/diff/1/components/data_reduction_p...
components/data_reduction_proxy/core/common/data_reduction_proxy_event_store_unittest.cc:175:
"Succeeded", 0, net::HTTP_OK, true, true,
nit: instead of using 0 for the net error, use net::OK, here and below.

[jeremyim, 2015-06-05 05:22:07]

https://codereview.chromium.org/1154623008/diff/1/components/data_reduction_p...
File
components/data_reduction_proxy/core/common/data_reduction_proxy_event_store_unittest.cc
(right):

https://codereview.chromium.org/1154623008/diff/1/components/data_reduction_p...
components/data_reduction_proxy/core/common/data_reduction_proxy_event_store_unittest.cc:175:
"Succeeded", 0, net::HTTP_OK, true, true,
On 2015/06/05 01:25:58, sclittle wrote:
> nit: instead of using 0 for the net error, use net::OK, here and below.

Done.

[jeremyim, 2015-06-05 05:22:29]

The CQ bit was checked by jeremyim@chromium.org

[jeremyim, 2015-06-05 05:22:30]

The patchset sent to the CQ was uploaded after l-g-t-m from
sclittle@chromium.org
Link to the patchset: https://codereview.chromium.org/1154623008/#ps20001
(title: "sclittle CR comment")

[commit-bot: I haz the power, 2015-06-05 05:22:42]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1154623008/20001

[commit-bot: I haz the power, 2015-06-05 06:11:58]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-06-05 06:12:54]

Patchset 2 (id:??) landed as
https://crrev.com/3f0baabb34dd8b112b8da00cb94f206b6f7717db
Cr-Commit-Position: refs/heads/master@{#333017}