Avoid calling into the ContentBrowserClient interface from ResourceDispatcherHostImpl to determine …

extensions/browser/bad_message.h

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef EXTENSIONS_BROWSER_BAD_MESSAGE_H_
 #define EXTENSIONS_BROWSER_BAD_MESSAGE_H_
 
 namespace content {
 class RenderProcessHost;
 }
@@ skipping 10 matching lines @@
 // end. Items may be renamed but do not change the values. We rely on the enum
 // values in histograms.
 enum BadMessageReason {
   EOG_BAD_ORIGIN = 0,
   EVG_BAD_ORIGIN = 1,
   BH_BLOB_NOT_OWNED = 2,
   EH_BAD_EVENT_ID = 3,
   AVG_BAD_INST_ID = 4,
   AVG_BAD_EXT_ID = 5,
   AVG_NULL_AVG = 6,
+  INVALID_ORIGIN = 7,

[Charlie Reis, 2016/08/10 20:44:02]

As mentioned before, we can't define a code here and call ReceivedBadMessage
from within content with it.  (Also, I should point out that it's nice to use
ReceivedBadMessage within content when possible, since we have better support
for magic signatures there than in these other bad_message.h files, which get
hit less often.)

   // Please add new elements here. The naming convention is abbreviated class
   // name (e.g. ExtensionHost becomes EH) plus a unique description of the
   // reason. After making changes, you MUST update histograms.xml by running:
   // "python tools/metrics/histograms/update_bad_message_reasons.py"
   BAD_MESSAGE_MAX
 };
 
 // Called when the browser receives a bad IPC message from an extension process.
 // Logs the event, records a histogram metric for the |reason|, and terminates
 // the process for |host|.
 void ReceivedBadMessage(content::RenderProcessHost* host,
                         BadMessageReason reason);
 
 }  // namespace bad_message
 }  // namespace extensions
 
 #endif  // EXTENSIONS_BROWSER_BAD_MESSAGE_H_