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

content/public/browser/navigation_handle.h

Index: content/public/browser/navigation_handle.h
diff --git a/content/public/browser/navigation_handle.h b/content/public/browser/navigation_handle.h
index 7f1e8ab7111b27370271d709a85602ea5242a041..a91f0018ad2770018828cc633c254d6525e7f6fa 100644
--- a/content/public/browser/navigation_handle.h
+++ b/content/public/browser/navigation_handle.h
@@ -89,9 +89,9 @@ class CONTENT_EXPORT NavigationHandle {
   // This corresponds to NavigationThrottle::WillSendRequest. They should not
   // be queried before that.
 
-  // Whether the navigation is a POST or a GET. This may change during the
-  // navigation when encountering a server redirect.
-  virtual bool IsPost() = 0;
+  // HTTP method of the navigation (i.e. a POST or a GET). This may change
+  // during the navigation when encountering a server redirect.
+  virtual const std::string& GetMethod() = 0;

[Łukasz Anforowicz, 2016/06/01 16:28:38]

Hmmm... does the IsPost -> GetMethod change still look good in light of the
discussion we had in the other, WIP CL [1]?  I believe that we can only deal
with "GET" and "POST" here, right?

[1] https://codereview.chromium.org/2022483003/

[Charlie Reis, 2016/06/01 23:46:32]

Heh.  I think we just need to pick an approach and document why, so that we
don't flip flop between them any further.  :)  I'm ok with either approach.

If we can't navigate to something other than a GET or a POST and we want to
enforce that embedders don't try to, then keeping it as a bool seems reasonable.
 Let's document it if so.

[Łukasz Anforowicz, 2016/06/02 22:07:04]

In this case, let me go back to NavigationHandle::IsPost :-).  I've also added a
comment explaining why we have IsPost rather than GetMethod.

 
   // Returns a sanitized version of the referrer for this request.
   virtual const Referrer& GetReferrer() = 0;