Add data reduction functionality to all platforms.

chrome/browser/net/chrome_network_delegate.cc

Index: chrome/browser/net/chrome_network_delegate.cc
diff --git a/chrome/browser/net/chrome_network_delegate.cc b/chrome/browser/net/chrome_network_delegate.cc
index a646f20deb88d04ccff658f65396823639108f45..3658d6dfb2bae0b1f372276255643e06d5a06bb2 100644
--- a/chrome/browser/net/chrome_network_delegate.cc
+++ b/chrome/browser/net/chrome_network_delegate.cc
@@ -134,15 +134,9 @@ void UpdateContentLengthPrefs(
       profile->IsOffTheRecord()) {
     return;
   }
-#if defined(OS_ANDROID) && defined(SPDY_PROXY_AUTH_ORIGIN)
-  // If Android ever goes multi profile, the profile should be passed so that
-  // the browser preference will be taken.
   bool with_data_reduction_proxy_enabled =
-      ProfileManager::GetActiveUserProfile()->GetPrefs()->GetBoolean(
+      profile->GetPrefs()->GetBoolean(
           data_reduction_proxy::prefs::kDataReductionProxyEnabled);

[mmenke, 2014/09/10 15:16:48]

Could we just move this into UpdateContentLengthPrefs?  My general feeling is
that, with the possible exception of actually configuring the pref, it makes the
most sense to either only read the pref in the component, or only read it in the
component, rather than to split the responsibility of checking it between the
two.

Does mean "UpdateContentLengthPrefs" has to distingush between local state
prefs, and per user prefs, which isn't lovely...but we have to do that, here,
anyways.

[Not at Google. Contact bengr, 2014/09/10 21:38:34]

Done.

In the future we want to move off of local state completely and only use the
profile specific prefs.

-#else
-  bool with_data_reduction_proxy_enabled = false;
-#endif
 
   data_reduction_proxy::UpdateContentLengthPrefs(received_content_length,
                                          original_content_length,