I love open source:
- Issue: https://github.com/bluesky-social/social-app/issues/6992
- PR: https://github.com/bluesky-social/social-app/pull/6993
- Issue: https://github.com/bluesky-social/social-app/issues/6992
- PR: https://github.com/bluesky-social/social-app/pull/6993
Comments
General question:
What do you think about Chrome's caching behaviour in such scenarios? Why is it not serving the files from cache on reloads?
https://bsky.app/profile/kojordan.com/post/3lcnupafhe22g
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.