Correcting the version field in the Chrome-Proxy header to be the chromium build and patch number.

android_webview/browser/aw_browser_context.cc

Index: android_webview/browser/aw_browser_context.cc
diff --git a/android_webview/browser/aw_browser_context.cc b/android_webview/browser/aw_browser_context.cc
index 4287b02514445696ed74f8dba84bf9ef92daf4de..cd5699c82a057f62e9a59b1983e75d09473e3c68 100644
--- a/android_webview/browser/aw_browser_context.cc
+++ b/android_webview/browser/aw_browser_context.cc
@@ -104,6 +104,8 @@ void AwBrowserContext::PreMainMessageLoopRun() {
               data_reduction_proxy::DataReductionProxyParams::kAllowed)));
   data_reduction_proxy_auth_request_handler_.reset(
       new DataReductionProxyAuthRequestHandler(
+          data_reduction_proxy::kClientAndroidWebview,
+          data_reduction_proxy::kAndroidWebViewProtocolVersion,

[sgurun-gerrit only, 2014/08/04 21:46:54]

why do you want to have a different protocol version for webview vs. chrome?
After all it is client (data reduction proxy component) & server  that wants to
be compatible

[sgurun-gerrit only, 2014/08/04 22:58:02]

himm safebrowsing signals is I think the reason? lgtm

           data_reduction_proxy_settings_->params()));
 #endif