Skip to content
New issue

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

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

Already on GitHub? # to your account

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
Milestone

Comments

@vojtajina
Copy link
Contributor

The right solution is to use SHA of the content.

@ghost ghost assigned vojtajina Apr 27, 2013
vojtajina added a commit that referenced this issue Dec 1, 2013
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)
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant