[Webkit-unassigned] [Bug 114738] 304s broken for main resources

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=114738

--- Comment #16 from Alexander Romanovich <alex at sirensclef.com> ---
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. (https://blog.chromium.org/2017/01/reload-reloaded-faster-and-leaner-page_26.html)
- 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?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170130/c1958b35/attachment-0001.html>