Add enableReferrers and enableHyperlinkAuditing to contentSettings.misc API.

chrome/browser/net/chrome_network_delegate.h

Index: chrome/browser/net/chrome_network_delegate.h
diff --git a/chrome/browser/net/chrome_network_delegate.h b/chrome/browser/net/chrome_network_delegate.h
index 9c75dd95a891c93979e77add9db9e19f534a8876..739c809c85335ab996f6ce087be1eda41a3e1c9c 100644
--- a/chrome/browser/net/chrome_network_delegate.h
+++ b/chrome/browser/net/chrome_network_delegate.h
@@ -8,6 +8,8 @@
 
 #include "base/basictypes.h"
 #include "base/memory/ref_counted.h"
+#include "base/memory/scoped_ptr.h"
+#include "chrome/browser/prefs/pref_member.h"
 #include "chrome/browser/profiles/profile.h"
 #include "net/base/network_delegate.h"
 
@@ -20,9 +22,13 @@ class ChromeNetworkDelegate : public net::NetworkDelegate {
  public:
   // If |profile_id| is the invalid profile, events will be broadcasted to all
   // profiles, otherwise, they will only be sent to the specified profile.
+  // |enable_referrers| is a PrefMember which should be bound to the profile's
+  // PrefService and moved to the IO thread. It can be NULL. This object will

[willchan no longer on Chromium, 2011/04/05 13:10:41]

Why are you allowing it to be NULL? Does it crash otherwise in tests? If
possible, it'd be nice if it were always non-NULL and you added a DCHECK to
enforce this. It makes new readers of the code have to think less and avoids
having to do NULL checks everywhere.

OIC why, it looks like you are passing in NULL for the system
ChromeNetworkDelegate. Is that really what you want to do? Should we be setting
the referer for system requests if an extension disables them?

[Bernhard Bauer, 2011/04/05 14:49:02]

Yeah, I thought about adding support for the pref in the system network delegate
as well, I just decided against doing it right now, as the preference is not
registered in Local State, and there is no client which would set it either. If
you think it's worthwhile though, I can re-add it.

It's also somewhat unlikely that not stripping the referrer from system requests
is going to leak information, as the referrers would probably have to be
explicitly specified anyway.

[willchan no longer on Chromium, 2011/04/05 15:06:18]

I think I'd prefer this, but I don't feel too strongly. I mostly like avoiding
NULL checks where possible since people often forget when they are necessary.
Heh, you never know :) What if we have a DomUI page for configuring system
settings (profile-agnostic), and it uses XHR? That would probably be a
non-profile associated URLRequestContext that might have a referrer.

[Bernhard Bauer, 2011/04/05 16:12:59]

Fair enough. Done.

+  // take ownership of it.
   explicit ChromeNetworkDelegate(
       ExtensionEventRouterForwarder* event_router,
       ProfileId profile_id,
+      BooleanPrefMember* enable_referrers,
       ProtocolHandlerRegistry* protocol_handler_registry);
   virtual ~ChromeNetworkDelegate();
 
@@ -41,6 +47,7 @@ class ChromeNetworkDelegate : public net::NetworkDelegate {
 
   scoped_refptr<ExtensionEventRouterForwarder> event_router_;
   const ProfileId profile_id_;
+  scoped_ptr<BooleanPrefMember> enable_referrers_;
   scoped_refptr<ProtocolHandlerRegistry> protocol_handler_registry_;
   DISALLOW_COPY_AND_ASSIGN(ChromeNetworkDelegate);
 };