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);

[ppi, 2014/06/04 16:23:59]

Do we currently get a load with net::LOAD_BYPASS_CACHE here or does it result in
net::LOAD_PREFERRING_CACHE?

[clamy, 2014/06/04 16:39:25]

It would seem that we end up with a net::LOAD_VALIDATE_CACHE. However the
comments hint that we should do a reload from origin, which corresponds to a
net::LOAD_BYPASS_CACHE. Nate, which policy should be used here?

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