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

content/browser/frame_host/render_frame_proxy_host.cc

Index: content/browser/frame_host/render_frame_proxy_host.cc
diff --git a/content/browser/frame_host/render_frame_proxy_host.cc b/content/browser/frame_host/render_frame_proxy_host.cc
index f4ba295b7add988c7c38c4620db9f4af7ab69cf1..0bbc1fce53ba0517beec84bbbf65ed3f694e4c4d 100644
--- a/content/browser/frame_host/render_frame_proxy_host.cc
+++ b/content/browser/frame_host/render_frame_proxy_host.cc
@@ -251,10 +251,12 @@ void RenderFrameProxyHost::OnOpenURL(
 
   // TODO(alexmos, creis): Figure out whether |params.user_gesture| needs to be
   // passed in as well.
+  // TODO(lukasza): https://crbug.com/344348: Plumb through POST data
+  // (and a non-null NavigationHandle?).

[clamy, 2016/05/19 16:08:00]

See my comment in RequestTransferURL in favor of not passing the
NavigationHandle but the post data and method directly. We should not
instantiate a NavigationHandle here (there are some timing issues with doing
it).

[Łukasz Anforowicz, 2016/05/19 18:06:59]

Done.

   frame_tree_node_->navigator()->RequestTransferURL(
       current_rfh, validated_url, site_instance_.get(), std::vector<GURL>(),
       params.referrer, ui::PAGE_TRANSITION_LINK, GlobalRequestID(),
-      params.should_replace_current_entry);
+      params.should_replace_current_entry, nullptr);
 }
 
 void RenderFrameProxyHost::OnRouteMessageEvent(