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

Changing a preprocessor should invalidate the cache #520

Closed
vojtajina opened this issue Apr 27, 2013 · 0 comments
Closed

Changing a preprocessor should invalidate the cache #520

vojtajina opened this issue Apr 27, 2013 · 0 comments
Labels
type: bug
Milestone
v0.12

Comments

@vojtajina
Copy link
Contributor

The right solution is to use SHA of the content.
@ghost ghost assigned vojtajina Apr 27, 2013
@vojtajina vojtajina mentioned this issue Apr 27, 2013
Closed
@vojtajina vojtajina mentioned this issue Jun 27, 2013
Closed
vojtajina added a commit that referenced this issue Dec 1, 2013
@vojtajina
feat(web-server): use SHA hash instead of timestamps
8276733 
Heavy caching relies on SHA of the content rather than mtime timestamps.

Benefits:
- touching a file (without changing content) does not re-fetch the file
- reverting a file does not re-fetch the file (browser will use the previous cache)
- changing preprocessor configuration does invalidate cache (Closes #520)
@cafesanu cafesanu mentioned this issue Jan 6, 2016
Closed
This was referenced Sep 27, 2018
Merged
Closed
This was referenced May 25, 2019
Closed
Merged
@renovate renovate bot mentioned this issue Sep 28, 2019
Merged
1 task
@renovate renovate bot mentioned this issue Oct 11, 2019
Merged
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug
Projects
None yet
Milestone
v0.12
Development

No branches or pull requests
1 participant
@vojtajina