Repository navigation
Fix/feed cache control - #11
Merged
Merged
Conversation
…ntrol: no-cache The Velopack feed (releases.*.json, RELEASES-*, assets.*.json) and the installers keep their names across releases and were uploaded without a Cache-Control header, so the CDN cached each copy with its default lifetime. Horizon 0.9.583 clients kept receiving a feed cached at the previous release and never saw 0.9.591. With no-cache the CDN revalidates against storage on each request. Packages are named by version and keep their current caching.
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
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.
No description provided.