Append Unix timestamp for cache invalidation - #33
Merged
Merged
Conversation
Member
|
Clever solution! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #32
Append the number of seconds since 1970-01-01 to the URLs of internal resources in order to force a re-request of JavaScript, CSS and HTML when the site is re-built. This is so that the HTML, CSS, and JS are always synchronised.
This is important because sometimes JavaScript will encounter a fatal error if the HTML is not what is expected.
Only internal links (I only found two) are targetted, because they aren't expected to change at site build time, but instead at a more controlled moment. We can always append the timestamp in future and this will invalidate any current caches.