Make revalidation to fail when received a redirect response

third_party/WebKit/Source/core/fetch/Resource.cpp

Index: third_party/WebKit/Source/core/fetch/Resource.cpp
diff --git a/third_party/WebKit/Source/core/fetch/Resource.cpp b/third_party/WebKit/Source/core/fetch/Resource.cpp
index 029779ee39d9a60a977f94adfd23063322fce7b8..32e830a7d6ad9480963b4f91de7b5e54a718dd2a 100644
--- a/third_party/WebKit/Source/core/fetch/Resource.cpp
+++ b/third_party/WebKit/Source/core/fetch/Resource.cpp
@@ -552,6 +552,9 @@ void Resource::setRevalidatingRequest(const ResourceRequest& request)
 
 void Resource::willFollowRedirect(ResourceRequest& newRequest, const ResourceResponse& redirectResponse)
 {
+    if (!m_revalidatingRequest.isNull()) {
+        revalidationFailed();

[Nate Chapin, 2016/05/27 17:10:43]

Would m_redirectChain.clear() suffice?

[hiroshige, 2016/05/31 06:24:46]

No.
Just clearing |m_redirectChain| doesn't prevent |m_redirectChain.clear()| in
responceReceived() after  Resource::willFollowRedirect() is called during
revalidation.

+    }

[kinuko, 2016/05/27 14:25:01]

nit: no { } for consistency

[hiroshige, 2016/05/31 13:09:31]

Done.

     newRequest.setAllowStoredCredentials(m_options.allowCredentials == AllowStoredCredentials);
     m_redirectChain.append(RedirectPair(newRequest, redirectResponse));
 }