Implement a ResourceThrottle for URL overriding in Chrome on Android.

chrome/browser/renderer_host/chrome_resource_dispatcher_host_delegate.cc

Index: chrome/browser/renderer_host/chrome_resource_dispatcher_host_delegate.cc
diff --git a/chrome/browser/renderer_host/chrome_resource_dispatcher_host_delegate.cc b/chrome/browser/renderer_host/chrome_resource_dispatcher_host_delegate.cc
index 87ce2ae01d9d52d4e828973dd79aa5d70e5c16d1..5a8408a544585c9d72be599a04a9cec144f9228a 100644
--- a/chrome/browser/renderer_host/chrome_resource_dispatcher_host_delegate.cc
+++ b/chrome/browser/renderer_host/chrome_resource_dispatcher_host_delegate.cc
@@ -25,6 +25,7 @@
 #include "chrome/browser/renderer_host/chrome_url_request_user_data.h"
 #include "chrome/browser/renderer_host/safe_browsing_resource_throttle.h"
 #include "chrome/browser/renderer_host/transfer_navigation_resource_throttle.h"
+#include "chrome/browser/renderer_host/should_ignore_navigation_resource_throttle.h"
 #include "chrome/browser/safe_browsing/safe_browsing_service.h"
 #include "chrome/browser/ui/auto_login_prompter.h"
 #include "chrome/browser/ui/login/login_prompt.h"
@@ -169,6 +170,10 @@ void ChromeResourceDispatcherHostDelegate::RequestBeginning(
     throttles->push_back(new OfflineResourceThrottle(
         child_id, route_id, request, resource_context));
 #endif
+
+#if defined(OS_ANDROID)
+    throttles->push_back(new ShouldIgnoreNavigationResourceThrottle(request));

[joth, 2012/05/11 15:34:13]

this looks like a good point to also make it conditional on a runtime flag, so
we can avoid this check if we're running in browser mode.

(or we invent a new #define to use here for the embedded API mode, but I think
the runtime maybe better as eventually we could even use this optimization in
API mode too if the client hasn't been set / hasn't overridden the callback)

[mkosiba (inactive), 2012/05/15 14:20:23]

But we need this in browser mode!

It _might_ make sense to use this instead of
browser_handles_top_level_navigations in  Chrome Frame (in which case we'd
probably need to make the addition of the throttle depend on some runtime flag)
but that's a separate change.

[joth, 2012/05/15 14:30:43]

Yep makes sense. As discussed I was getting mixed up with the resource request
intercept case (again).

+#endif
   }
 
   AppendChromeMetricsHeaders(request, resource_context, resource_type);