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

content/browser/frame_host/render_frame_host_manager.cc

Index: content/browser/frame_host/render_frame_host_manager.cc
diff --git a/content/browser/frame_host/render_frame_host_manager.cc b/content/browser/frame_host/render_frame_host_manager.cc
index 89ba63c4521b0131ae14c4ae32c2be764ae8534a..14315b5aa5408f060986c63d293cadb82cca30d7 100644
--- a/content/browser/frame_host/render_frame_host_manager.cc
+++ b/content/browser/frame_host/render_frame_host_manager.cc
@@ -429,7 +429,8 @@ void RenderFrameHostManager::OnCrossSiteResponse(
     const std::vector<GURL>& transfer_url_chain,
     const Referrer& referrer,
     ui::PageTransition page_transition,
-    bool should_replace_current_entry) {
+    bool should_replace_current_entry,
+    const scoped_refptr<ResourceRequestBody>& resource_request_body) {
   // We should only get here for transfer navigations.  Most cross-process
   // navigations can just continue and wait to run the unload handler (by
   // swapping out) when the new navigation commits.
@@ -483,7 +484,8 @@ void RenderFrameHostManager::OnCrossSiteResponse(
       ->navigator()
       ->RequestTransferURL(transferring_render_frame_host, transfer_url,
                            nullptr, rest_of_chain, referrer, page_transition,
-                           global_request_id, should_replace_current_entry);
+                           global_request_id, should_replace_current_entry,
+                           resource_request_body);
 
   // The transferring request was only needed during the RequestTransferURL
   // call, so it is safe to clear at this point.