Apply Referrer-Policy header when following redirects

chrome/browser/profiles/profile_io_data.cc

Index: chrome/browser/profiles/profile_io_data.cc
diff --git a/chrome/browser/profiles/profile_io_data.cc b/chrome/browser/profiles/profile_io_data.cc
index b320a33ef9bc85aa1c530410c0dbfba60615b137..395dfa2b218018b07752d4ff7059ac38d2f6be1a 100644
--- a/chrome/browser/profiles/profile_io_data.cc
+++ b/chrome/browser/profiles/profile_io_data.cc
@@ -80,6 +80,7 @@
 #include "content/public/browser/host_zoom_map.h"
 #include "content/public/browser/notification_service.h"
 #include "content/public/browser/resource_context.h"
+#include "content/public/common/content_switches.h"
 #include "net/base/keygen_handler.h"
 #include "net/cert/cert_verifier.h"
 #include "net/cert/ct_log_verifier.h"
@@ -1029,6 +1030,11 @@ void ProfileIOData::Init(
 
   main_request_context_->set_enable_brotli(io_thread_globals->enable_brotli);
 
+  // TODO(estark): Remove this once the Referrer-Policy header is no
+  // longer an experimental feature. https://crbug.com/619228
+  main_request_context_->set_enable_referrer_policy_header(
+      command_line.HasSwitch(switches::kEnableExperimentalWebPlatformFeatures));

[jochen (gone - plz use gerrit), 2016/06/27 08:33:40]

how will this work in content shell?

[mmenke, 2016/06/27 18:38:05]

I don't think we normally enable experimental features on content shell, do we? 
When we finally enable it unconditionally, we're remove all the code to
conditionally enable it.  i.e., the bool to enable / disable it will be removed,
so content shell won't need to be updated.

[jochen (gone - plz use gerrit), 2016/06/28 13:03:46]

content_shell is run with both test-only and experimental features enabled for
layout tests

+
   std::unique_ptr<ChromeNetworkDelegate> network_delegate(
       new ChromeNetworkDelegate(
 #if defined(ENABLE_EXTENSIONS)