Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Investigate caching issues #556

Open
RReverser opened this issue May 27, 2021 · 2 comments
Open

Investigate caching issues #556

RReverser opened this issue May 27, 2021 · 2 comments
Labels
meta Issues involving the build process or the website itself, rather than its content

Comments

@RReverser
Copy link
Contributor

Looks like whenever we update CSS, it's not properly updated right away on clients - either due to Chrome's own aggressive caching, or our usage of Service Workers.

This leads to issues like this: https://twitter.com/RReverser/status/1397952567213268994.

/cc @mathiasbynens in case you have quick ideas
@mathiasbynens mathiasbynens added the meta Issues involving the build process or the website itself, rather than its content label May 28, 2021
@mathiasbynens
Copy link
Member

Maybe we should cache-bust by serving main.hash.css instead of main.css?

@mathiasbynens
Copy link
Member

(That's assuming the problem is Chrome's own caching rather than the service worker — I didn’t check!)

@Brecheyashtiff Brecheyashtiff mentioned this issue Jul 19, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
meta Issues involving the build process or the website itself, rather than its content
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mathiasbynens @RReverser