<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - 304s broken for main resources"
href="https://bugs.webkit.org/show_bug.cgi?id=114738#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - 304s broken for main resources"
href="https://bugs.webkit.org/show_bug.cgi?id=114738">bug 114738</a>
from <span class="vcard"><a class="email" href="mailto:alex@sirensclef.com" title="Alexander Romanovich <alex@sirensclef.com>"> <span class="fn">Alexander Romanovich</span></a>
</span></b>
<pre>Note that with Chrome 56, the behavior between Chrome and Safari has diverged even further.
It appears that now Chrome:
- Revalidates only the main resource on refresh. (<a href="https://blog.chromium.org/2017/01/reload-reloaded-faster-and-leaner-page_26.html">https://blog.chromium.org/2017/01/reload-reloaded-faster-and-leaner-page_26.html</a>)
- Revalidates all other resources with a shift-refresh.
- Supports 304s on the main resource (as before).
And Safari:
- Revalides all resources on refresh (i.e. always shift-refreshes).
- Still does not support 304s on the main resource.
I wonder if support for 304s on main resources could be given attention again in the context of the broader context of Chrome's recent decision, and the fact that Safari does not support shift-refresh?</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>