Add functionality for specifying a web cache expiration #60
Conversation
This file contains 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
This commit allows the Redis and web cache expiration to be set independently.
|
This looks really nice. It is just sad that this project has been discontinued. |
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.
It should be possible to use the
cache-controlheader'sno-cachedirective to force web caches to revalidate cached results before providing them. Unfortunately, some proxy caches do not appear to respectno-cache, and will continue to provide results from cache until they have expired.This commit allows the Redis and web cache expirations to be set independently, so that items can be cached to Redis with long expirations, but provided to the web with shorter expirations, forcing web caches to revalidate.