Added support for an automatic cache buster suffix on the bg image#56
Merged
aslansky merged 1 commit intoaslansky:masterfrom Mar 12, 2015
michaelmoussa:cache-busting
Merged
Added support for an automatic cache buster suffix on the bg image#56aslansky merged 1 commit intoaslansky:masterfrom michaelmoussa:cache-busting
aslansky merged 1 commit intoaslansky:masterfrom
michaelmoussa:cache-busting
Conversation
aslansky
added a commit
that referenced
this pull request
Mar 12, 2015
Added support for an automatic cache buster suffix on the bg image
Contributor
Author
|
Thanks! :) |
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
3 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.
Folks who use a CDN can append their own cache buster to the
.cssfile, but thebackground-imageentry in the CSS file would still end up being loaded from the browser cache.This change adds support for a
--cachebuster=randomparameter, which will append?<hash>to thebackground-image: url(...), where<hash>is a randomly generated 40-character hexadecimal string. This would force the new, possibly updated sprite file to be downloaded freshly.