PlzNavigate: make NavigationResourceHandler a LayeredResourceHandler

content/browser/frame_host/navigation_request.cc

Index: content/browser/frame_host/navigation_request.cc
diff --git a/content/browser/frame_host/navigation_request.cc b/content/browser/frame_host/navigation_request.cc
index e4f6850a6c143a055c4fe7fabc3d3bed73a9043c..3b1f9230c79c0403079fc3f5e54d52728e003c99 100644
--- a/content/browser/frame_host/navigation_request.cc
+++ b/content/browser/frame_host/navigation_request.cc
@@ -793,6 +793,11 @@ void NavigationRequest::OnWillProcessResponseChecksComplete(
     NavigationThrottle::ThrottleCheckResult result) {
   DCHECK(result != NavigationThrottle::DEFER);
 
+  // If the NavigationThrottles allowed the navigation to continue, have the
+  // processing of the response resume in the network stack.
+  if (result == NavigationThrottle::PROCEED)
+    loader_->ProceedWithResponse();

[mmenke, 2017/04/28 16:02:20]

Why move this?  This seems to be exclusive to the next two branches, which both
also have early returns, so this seems to make no difference.

[clamy, 2017/05/02 15:05:44]

Because in the case of downloads response_should_be_rendered_ should be rendered
is false, but we need the load to proceed in the network stack.

[mmenke, 2017/05/02 15:55:39]

Thanks!  Missed that case.

+
   // Abort the request if needed. This includes requests that were blocked by
   // NavigationThrottles and requests that should not commit (e.g. downloads,
   // 204/205s). This will destroy the NavigationRequest.
@@ -813,9 +818,6 @@ void NavigationRequest::OnWillProcessResponseChecksComplete(
     return;
   }
 
-  // Have the processing of the response resume in the network stack.
-  loader_->ProceedWithResponse();
-
   CommitNavigation();
 
   // DO NOT ADD CODE after this. The previous call to CommitNavigation caused