Allow navigations performed by extensions to pass through AllowExtensionResourceLoad.

chrome/browser/extensions/extension_protocols.cc

Index: chrome/browser/extensions/extension_protocols.cc
diff --git a/chrome/browser/extensions/extension_protocols.cc b/chrome/browser/extensions/extension_protocols.cc
index 217afa83238ef10c5bead8fe22719a03ab59f6de..2c184370b739c01f8f3f6b977f5adce6441d65bf 100644
--- a/chrome/browser/extensions/extension_protocols.cc
+++ b/chrome/browser/extensions/extension_protocols.cc
@@ -370,6 +370,12 @@ bool AllowExtensionResourceLoad(net::URLRequest* request,
     return true;
   }
 
+  // If the request is for navigations, then it should be allowed. The
+  // navigation logic in CrossSiteResourceHandler will properly transfer the
+  // navigation to a privileged process before it commits.
+  if (ResourceType::IsFrame(info->GetResourceType()))

[Matt Perry, 2013/11/01 19:16:10]

Does this mean an arbitrary webpage can navigate an iframe to a chrome-extension
URL? Can it detect success or failure? If so, that's not good - it's why we have
the web-accessible-resource check below.

+    return true;
+
   // Extensions with webview: allow loading certain resources by guest renderers
   // with privileged partition IDs as specified in the manifest file.
   ExtensionRendererState* renderer_state =