Use the ReloadBypassingCache policy

Source/core/loader/DocumentLoader.cpp

Index: Source/core/loader/DocumentLoader.cpp
diff --git a/Source/core/loader/DocumentLoader.cpp b/Source/core/loader/DocumentLoader.cpp
index db2b2ce35833cd725be34e5edd301bd5b2f3f703..be435a98c8f85d963c4048cf1e45f0e563f569db 100644
--- a/Source/core/loader/DocumentLoader.cpp
+++ b/Source/core/loader/DocumentLoader.cpp
@@ -371,7 +371,7 @@ void DocumentLoader::willSendRequest(ResourceRequest& newRequest, const Resource
     // this is a common site technique to return to a page viewing some data that the POST
     // just modified.
     if (newRequest.cachePolicy() == UseProtocolCachePolicy && isRedirectAfterPost(newRequest, redirectResponse))
-        newRequest.setCachePolicy(ReloadIgnoringCacheData);
+        newRequest.setCachePolicy(ReloadBypassingCache);

[Nate Chapin, 2014/06/04 16:43:56]

We have used ReloadIgnoringCacheData as long as I can remember, but based on the
comment and my understanding of how web pages use these redirects,
ReloadBypassingCache probably makes more sense.

 
     // If this is a sub-frame, check for mixed content blocking against the top frame.
     if (m_frame->tree().parent()) {