OpenURL post data handling.

content/common/frame_messages.h

 // Copyright 2013 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // IPC messages for interacting with frames.
 // Multiply-included message file, hence no include guard.
 
 #include <stddef.h>
 #include <stdint.h>
 
@@ skipping 430 matching lines @@
   // Specifies properties for a new RenderWidget that will be attached to the
   // new RenderFrame (if one is needed).
   IPC_STRUCT_MEMBER(FrameMsg_NewFrame_WidgetParams, widget_params)
 IPC_STRUCT_END()
 
 // Parameters included with an OpenURL request.  |frame_unique_name| is only
 // specified if |is_history_navigation_in_new_child| is true, for the case that
 // the browser process should look for an existing history item for the frame.
 IPC_STRUCT_BEGIN(FrameHostMsg_OpenURL_Params)
   IPC_STRUCT_MEMBER(GURL, url)
+  IPC_STRUCT_MEMBER(bool, uses_post)
+  IPC_STRUCT_MEMBER(scoped_refptr<content::ResourceRequestBodyImpl>,
+                    resource_request_body)

[Łukasz Anforowicz, 2016/06/10 20:00:49]

Note that this is not the first time when we send ResourceRequestBody back into
the renderer process (i.e. we already do it in
content::ResourceRequest::request_body embedded in
ResourceHostMsg_RequestResource and a few other IPC messages).

This *is* the first time when ResourceRequestBody is passed above //content
layer, into the embedder.  OTOH, above //content ResourceRequestBody is opaque
[1], so I think we shouldn't be getting any extra exposure here.

[1] e.g. see the class comment in content/public/common/resource_request_body.h
in https://codereview.chromium.org/2038813003/patch/40001/50059

[nasko, 2016/06/10 20:22:28]

FrameHostMsg_OpenURL_Params cannot be seen outside of content/, so I don't think
adding the Impl to this IPC message is a problem. The handler of the IPC that
sends the results of it outside of content/ should be the one ensuring we only
expose the public interface.

   IPC_STRUCT_MEMBER(content::Referrer, referrer)
   IPC_STRUCT_MEMBER(WindowOpenDisposition, disposition)
   IPC_STRUCT_MEMBER(bool, should_replace_current_entry)
   IPC_STRUCT_MEMBER(bool, user_gesture)
   IPC_STRUCT_MEMBER(bool, is_history_navigation_in_new_child)
   IPC_STRUCT_MEMBER(std::string, frame_unique_name)
 IPC_STRUCT_END()
 
 IPC_STRUCT_BEGIN(FrameMsg_TextTrackSettings_Params)
   // Text tracks on/off state
@@ skipping 1015 matching lines @@
 IPC_MESSAGE_ROUTED3(FrameHostMsg_FindMatchRects_Reply,
                     int /* version */,
                     std::vector<gfx::RectF> /* rects */,
                     gfx::RectF /* active_rect */)
 #endif
 
 // Adding a new message? Stick to the sort order above: first platform
 // independent FrameMsg, then ifdefs for platform specific FrameMsg, then
 // platform independent FrameHostMsg, then ifdefs for platform specific
 // FrameHostMsg.