[Webkit-unassigned] [Bug 209961] request gets fetched from memory cache instead of service worker after second refresh

[bugzilla-daemon at webkit.org]

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

--- Comment #4 from youenn fablet <youennf at gmail.com> ---
(In reply to Giorgi from comment #3)
> Question 1)
> 
> It's really interesting why the same thing doesn't happen on chrome and
> what's the reason they decided not to use this flow. Of course, they use
> memory cache but if there's service worker in play, service worker starts to
> be in full control and assets don't get returned from memory cache in this
> case. 

Memory cache is not yet standardised so it is not surprising to see differences in that area.

> Question 2)
> 
> Exactly which Cache-Control attribute would you use in this case ?

I would probably use something like must-revalidate.
The service worker would always get the request.
The service worker could return a 304 to make use of the memory cache entry.

-- 
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/20200404/0db1e151/attachment.htm>