Re: [whatwg/fetch] Define the "Preload Cache" (#590)

> I don't think we should tie preload to any specific cache headers. That doesn't seem web compatible, nor what we'd want.
> At the same time, I think that what you proposed above would work for one-time use, which is the majority case.

In a way current preload is not compatible with existing cache headers - preloading something that has `no-cache` which might return a different value when actually fetched.

I believe that if we don't tie preload to cache headers at all, then we should say that it trumps cache headers - not just for the "first load" - meaning that if you preloaded something it stays in the preload list regardless of whether its content on the server might have changed, and is treated as if it was immutable (during the lifetime of the `link` element). I wonder how compatible it is with the intent of something like [fetch Request cache mode](https://developer.mozilla.org/en-US/docs/Web/API/Request/cache). 


-- 
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/issues/590#issuecomment-927568728