Chrome Version: M58
OS: N/A

hiroshige@ pointed to me that that link preloads might be unnecessarily bypassing checks in ResourceFetcher::determineRevalidationPolicy.

There are two checks there for isPreloaded(). The first is conditional on the forPreload() flag, which indicates a speculative preload, and seems to be fine.

The second is only related to link preload preloaded resources. There are a few checks after that check, which might be important to revalidate even for link preloads:
* allowStoredCredentials match. We should make sure that matches for all requests.
* Vary header existence. I'd claim that this is important to revalidate only for cases where the request includes non default headers (headers set by XHR/fetch & client hints headers)

hiroshige@ - do you see any other checks that I missed and that should be applied to link preloads?