Warning about appcache getting fed standard cache #14
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.
The
?rel=324784983
querystrings are misleading, this is NOT a reliable method of cache busting. (So I removed them) This is something the developer needs to know about and since grunt-contrib-manifest is only concerned with generating the manifest. However, grunt-contrib-manifest could match rails md5 hash algorithm to hit the right files, same thing with yeoman, and there could be a setting to add the file hash before or after the filename (but always before the extension of course) There could also be a setting to add the file hash at the root like:domain.com/hash/actual/path/to/file.js
this scheme may be easier to support for say, node.js