[Webkit-unassigned] [Bug 239093] New: Different caching behavior for .wasm files when refreshing with the reload button
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Apr 11 15:52:28 PDT 2022
https://bugs.webkit.org/show_bug.cgi?id=239093
Bug ID: 239093
Summary: Different caching behavior for .wasm files when
refreshing with the reload button
Product: WebKit
Version: Safari 15
Hardware: All
OS: macOS 12
Status: NEW
Severity: Normal
Priority: P2
Component: Website Storage
Assignee: webkit-unassigned at lists.webkit.org
Reporter: susan at figma.com
CC: sihui_liu at apple.com
Using this page as an example, https://www.figma.com/file/z1Q0Jea05gibeGQyasrJd6/TEST?node-id=0%3A1
This page fetches two .wasm files from network.
When I press the reload button rightmost of the address bar, the caching for these two files differ.
In my testing, one of them always caches, on disk. But the other one never caches. All js resources would cache.
My iPhone 7 has the same behavior -- I saw the same pattern when I'm inspecting from the 'Develop' menu in my Desktop Safari when connected to my phone.
Occasionally, from a fresh tab, when I reload using the reload icon, both files are fetching from memory for the first time, but subsequent refreshes would miss again.
This behavior sounds extremely similar to another user's observation: https://developer.apple.com/forums/thread/125224, search for "Should I log a bug for this".
For both Desktop and iPhone, when I click and enter from the address bar directly, however, the two .wasm files would be cached.
When I open the file in private browsing on desktop, I noticed that these two .wasm files never cache when I reload with the reload icon.
It is surprising to me that in the non-private browsing case, the browser caches the .wasm files differently, when they are served with the exact same cache control headers from the same server.
Moreover, the js resources would always cache. Are js files treated differently from the .wasm file type?
I'm on Safari Version 15.2, macOS Monterey 12.1.
The iPhone I mentioned is an iPhone 7, Safari Version 15.3 (inferred from the user agent string).
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220411/9d30709a/attachment-0001.htm>
More information about the webkit-unassigned
mailing list