Executed HTTPS upgrade before notifying the start of the provisional load.

third_party/WebKit/Source/core/loader/FrameLoader.cpp

Index: third_party/WebKit/Source/core/loader/FrameLoader.cpp
diff --git a/third_party/WebKit/Source/core/loader/FrameLoader.cpp b/third_party/WebKit/Source/core/loader/FrameLoader.cpp
index 73b5374e1fb259a7c7e283ebc37fa32fa832e0c7..0e1e459be69aa895b8dff6b3475324274d0a35e5 100644
--- a/third_party/WebKit/Source/core/loader/FrameLoader.cpp
+++ b/third_party/WebKit/Source/core/loader/FrameLoader.cpp
@@ -1455,6 +1455,7 @@ void FrameLoader::startLoad(FrameLoadRequest& frameLoadRequest, FrameLoadType ty
     if (m_provisionalDocumentLoader->isClientRedirect())
         m_provisionalDocumentLoader->appendRedirect(m_frame->document()->url());
     m_provisionalDocumentLoader->appendRedirect(m_provisionalDocumentLoader->request().url());
+    m_provisionalDocumentLoader->upgradeInsecureRequest();

[carlosk, 2016/06/28 14:44:32]

This was the best way I found to execute the upgrading from here. Other options
I considered were:

- Create an early FrameFetchContext: but it needs a DocumentLoader instance
(chicken and egg situation).
- Make FrameFetchContext::upgradeInsecureRequest static: would expose the whole
document vs loader checks and that didn't look good.
- Add a non-cost getter from the DocumentLoader's request: the loader already
does a lot of modifications of the request internally and the call now enclosed
in DocumentLoader::upgradeInsecureRequest looks better there than here.

     double triggeringEventTime = frameLoadRequest.triggeringEvent() ? frameLoadRequest.triggeringEvent()->platformTimeStamp() : 0;
     client()->dispatchDidStartProvisionalLoad(triggeringEventTime);
     ASSERT(m_provisionalDocumentLoader);