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.

@annevk I've added a not null condition to the if clause.

@jakearchibald That was largely a debate that was before for Chrome where SWR is implemented and having it at the top level (instead of the cache level) had these issues but provides the cancelibility that is desirable when a page terminates all outstanding requests terminate. Developers really shouldn't be relying on caching for functionality. 

For OCSP and downloads it doesn't make sense to do it for because they don't affect the initial display of the page which is what largely this feature targets. Do these requests without a client go through service workers as well?

-- 
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_r276665837