<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Inconsistencies in main resource load delegates when loading from history"
href="https://bugs.webkit.org/show_bug.cgi?id=150927#c20">Comment # 20</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Inconsistencies in main resource load delegates when loading from history"
href="https://bugs.webkit.org/show_bug.cgi?id=150927">bug 150927</a>
from <span class="vcard"><a class="email" href="mailto:cgarcia@igalia.com" title="Carlos Garcia Campos <cgarcia@igalia.com>"> <span class="fn">Carlos Garcia Campos</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=150927#c18">comment #18</a>)
<span class="quote">> Another thing that we discussed was that it sounds like an actual bug if SSL
> certificate is forgotten in UI process before the next loads commits (which
> was what prompted this investigation).</span >
The actual problem is that we don't have a main resource when load is committed. It's not that the certificate is lost, it's that we use the response of the main resource to get the certificate info, and we say in our docs that when the load is committed is the moment to ask for the certificate. Because for a load to be committed we need to have a main resource load and response from the server. That's true in all the cases expect for history loads with page cache enabled.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>