What I figured out though: The `Vary: Origin` response header seems to prevent using the cache, when alternating cors/no-cors requests occur, since only the cors requests send the `Origin` header.
-I wasn't aware that for `Vary`ing requests for the same URL, Chrome doesn't seem to store and serve a separate cache entry for each varying value.
-Firefox only sends an `Origin` header when the request is actually cross-origin?
-Good to know that the issue for preloaded fonts is pretty rare.
Comments
What I figured out though: The `Vary: Origin` response header seems to prevent using the cache, when alternating cors/no-cors requests occur, since only the cors requests send the `Origin` header.
Some additional thoughts:
-Firefox only sends an `Origin` header when the request is actually cross-origin?
-Good to know that the issue for preloaded fonts is pretty rare.