This question was asked a while ago: https://support.mozilla.org/en-US/questions/1267945 asking what the "(raced)" values were inside the Transferred column of the Networ… (閱讀更多)
This question was asked a while ago: https://support.mozilla.org/en-US/questions/1267945 asking what the "(raced)" values were inside the Transferred column of the Network tab in the Developer Tools.
In short, it sounds like when the browser detects a slow pull of a value from the local cache, it "races" the cache by actually making the network request to see which comes back first to provide the fastest loading possible for the end user.
While conceptually I totally get this, as a Web Developer I'm now curious if this particular network request identifies itself in some way via HTTP Header values?
We actively seek out customers of our web applications to see which ones have "bad" cache settings (no cache, too small a cache, or flushed constantly) to reach out to them to resolve this (and/or find out the reason why they were disabling their cache). TL;DR - I think these RCWN requests may give us a false positive when trying to detect users with bad cache settings... so I'd like to be able to "ignore" these RCWN requests in our analysis (I don't want to block or otherwise interfere with these requests).
On a secondary note, is there any info for the end user on why a given resource was raced? It appears that all of the "(raced)" resources I'm seeing on my frequently visited sites are less than 2.5KB (often under 1 KB) - just wondering if the algorithm to detect "slow" resources is properly scaled for small resources.