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

@dtapuska you seem to be conflating "the request allows stale content" and "the use of stale content will kick off a revalidating request asynchronously." The former is `max-stale` in [HTTP caching](https://httpwg.org/specs/rfc7234.html#cache-request-directive.max-stale); the latter is `stale-while-revalidate`.

I was concerned about similar things to @jakearchibald above in #852; HTTP already defines how responses can be used for SwR, but there's no hint of that here. 

@annevk this seems to be a recurring pattern; HTTP defines what happens on the wire, and Fetch defines a corresponding API for each feature. If that's going to be normal going forward, it'd probably be best to document the division of labour (as it were) so that people don't get confused.

Also, it'd be good to get alignment on whether or not browsers pay attention to request `Cache-Control` (see [tests](https://cache-tests.fyi/#cc-request)) and how that interacts with these Fetch directives.


-- 
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#issuecomment-465002152