Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853)

dtapuska commented on this pull request.



> +         "<code>no-cache</code>".
+
+         <li><p>Set <var>revalidateRequest</var>'s
+         <a for=request>prevent no-cache cache-control header modification flag</a>.
+
+         <li><p>Set <var>revalidateRequest</var>'s <a for=request>service-workers mode</a> set to
+         "<code>none</code>".
+
+         <li>
+          <p><a>In parallel</a>, perform <a for=main>main fetch</a> using
+          <var>revalidateRequest</var>.
+
+          <p class=note>This fetch is only meant to update the state of the HTTP cache and the
+          response will be unused until another cache access. The stale response will be used as the
+          response to current request. This fetch is issued in the context of a client so if it goes
+          away the request will be terminated.

It would still be revalidated but it would just be done after expiry and revalidated synchronously (basically ignoring swr directive) on the next fetch of it. It would be nice to hear from Gecko what they did.  But I downloads nor OCSP likely hit the cache in Chrome anyways so it is probably an even more limited set of fetches that are unknown.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/853#discussion_r276675279