Index: content/browser/loader/navigation_resource_throttle.cc |
diff --git a/content/browser/loader/navigation_resource_throttle.cc b/content/browser/loader/navigation_resource_throttle.cc |
index e9c8e269d89405ca9380261f521ff1c5ebf18797..2a6aa9f3764ff6820f17b1a40aac3dfd04b144c6 100644 |
--- a/content/browser/loader/navigation_resource_throttle.cc |
+++ b/content/browser/loader/navigation_resource_throttle.cc |
@@ -343,6 +343,16 @@ void NavigationResourceThrottle::OnUIChecksPerformed( |
controller()->Cancel(); |
} else if (result == NavigationThrottle::BLOCK_REQUEST) { |
controller()->CancelWithError(net::ERR_BLOCKED_BY_CLIENT); |
+ } else if (result == NavigationThrottle::BLOCK_RESPONSE) { |
+ // TODO(mkwst): If we cancel the main frame request with anything other than |
+ // 'net::ERR_ABORTED', we'll trigger some special behavior that might not be |
+ // desirable here (non-POSTs will reload the page, while POST has some logic |
+ // around reloading to avoid duplicating actions server-side). For the |
+ // moment, only child frame navigations should be blocked. If we need to |
+ // block main frame navigations in the future, we'll need to carefully |
+ // consider the right thing to do here. |
+ DCHECK(!ResourceRequestInfo::ForRequest(request_)->IsMainFrame()); |
+ controller()->CancelWithError(net::ERR_BLOCKED_BY_RESPONSE); |
} else { |
controller()->Resume(); |
} |