Add data reduction functionality to all platforms.

net/http/http_log_util.cc

Index: net/http/http_log_util.cc
diff --git a/net/http/http_log_util.cc b/net/http/http_log_util.cc
index 4d0e6e98ce81d1e44c73727a4094e5c5a8784943..97282dcd15a0e82422f68585608cc662feab68d3 100644
--- a/net/http/http_log_util.cc
+++ b/net/http/http_log_util.cc
@@ -34,7 +34,6 @@ bool ShouldRedactChallenge(HttpAuthChallengeTokenizer* challenge) {
 
 }  // namespace
 
-#if defined(SPDY_PROXY_AUTH_ORIGIN)
 void ElideChromeProxyDirective(const std::string& header_value,
                                const std::string& directive,
                                std::string::const_iterator* redact_begin,
@@ -50,18 +49,15 @@ void ElideChromeProxyDirective(const std::string& header_value,
     }
   }
 }

[Ryan Sleevi, 2014/08/28 17:21:01]

You still haven't removed/resolved this, which is a core concern that I raised.

[Not at Google. Contact bengr, 2014/08/28 18:59:28]

This is the only remainging layer violation. I thought we agreed that while this
is very important, it wasn't worth blocking the rest of this cl over. I have bug
https://code.google.com/p/chromium/issues/detail?id=396807 filed against me for
this purpose, and will get to this next. Prefer getting this cl in and then
fixing this violation.

[Ryan Sleevi, 2014/09/02 19:30:10]

M-38 has shipped. This code is for M-39, that bug is targetted for M39, I would
want to see how you intend to solve this for M39, at the least, to be
comfortable accepting new technical debt into this.

Again, to reiterate, my very real concern is that once you launch this, with the
whole host of new issues that desktop (and ChromeOS, even if that's all this
targets) introduce, and that you will spend your time chasing down bugs or
regressions rather than getting to that.

Considering this has happened in the past several times, I feel it's important
that we do the right thing here, especially with several weeks left of M39.

[Not at Google. Contact bengr, 2014/09/04 22:45:40]

I am in the process of finding an approach to this with help from net-dev.

Is this the only outstanding issue for this cl? If not, can you please review
the rest of it so that once we remove the layering violation in this file, this
cl is good to go.

This cl is the first of a few we need to land to have the Flywheel working on
desktop in M39, so this cl needs to land as soon as possible rather than towards
the end of M39.

-#endif
 
 std::string ElideHeaderValueForNetLog(NetLog::LogLevel log_level,
                                       const std::string& header,
                                       const std::string& value) {
   std::string::const_iterator redact_begin = value.begin();
   std::string::const_iterator redact_end = value.begin();
-#if defined(SPDY_PROXY_AUTH_ORIGIN)
   if (!base::strcasecmp(header.c_str(), "chrome-proxy")) {

[Ryan Sleevi, 2014/08/28 17:21:01]

This is still a layering violation.

[Not at Google. Contact bengr, 2014/08/28 18:59:28]

Same as above.

     ElideChromeProxyDirective(value, "sid=", &redact_begin, &redact_end);
   }
-#endif
 
   if (redact_begin == redact_end &&
       log_level >= NetLog::LOG_STRIP_PRIVATE_DATA) {