Forwarding POST body into renderer after a cross-site transfer.

content/browser/frame_host/navigator_impl.cc

Index: content/browser/frame_host/navigator_impl.cc
diff --git a/content/browser/frame_host/navigator_impl.cc b/content/browser/frame_host/navigator_impl.cc
index 6fcdb074b4a0f6badd1ea04256214a7e2223480d..c58916e9a5285709aa106870ad0532854f7ca24c 100644
--- a/content/browser/frame_host/navigator_impl.cc
+++ b/content/browser/frame_host/navigator_impl.cc
@@ -707,7 +707,8 @@ void NavigatorImpl::RequestTransferURL(
     const Referrer& referrer,
     ui::PageTransition page_transition,
     const GlobalRequestID& transferred_global_request_id,
-    bool should_replace_current_entry) {
+    bool should_replace_current_entry,
+    const scoped_refptr<ResourceRequestBody>& resource_request_body) {
   // This call only makes sense for subframes if OOPIFs are possible.
   DCHECK(!render_frame_host->GetParent() ||
          SiteIsolationPolicy::AreCrossProcessFramesPossible());
@@ -812,6 +813,11 @@ void NavigatorImpl::RequestTransferURL(
         static_cast<SiteInstanceImpl*>(source_site_instance), dest_url,
         referrer_to_use, "GET", -1);
   }
+
+  // TODO(lukasza): DO NOT SUBMIT: Plumb |resource_request_body| further.
+  // Option #1: Conjure a new page state and add the body into the page state?
+  // Option #2: Add the body to either FrameNav...Entry or NavigationEntryImpl.

[Łukasz Anforowicz, 2016/05/10 00:49:37]

I haven't quite wrapped my head yet around option #1 - this option seems most
compatible with clamy@'s PlzNavigate CL (where post data is being extracted from
PageState), but I don't know how to construct or mutate a PageState in order to
populate its POST body.

+
   NavigateToEntry(node, *frame_entry, *entry.get(),
                   NavigationController::NO_RELOAD, false, false);
 }