Restore the original behavior of 'x-apicache-force-fetch' header #220
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
The behaviors of 'x-apicache-force-fetch' and 'x-apicache-bypass' have become the same for no reason. This commit restores the original behavior of 'x-apicache-force-fetch' which was to force data fetch AND update the cache with new data ... while 'x-apicache-bypass' completely bypasses the apicache middleware.
|
CI errors have nothing to do with my commit ... :( |
This was referenced Aug 7, 2020
msieurtoph
changed the title
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.
The behaviors of 'x-apicache-force-fetch' and 'x-apicache-bypass' have become the same for no reason.
This commit restores the original behavior of 'x-apicache-force-fetch' which was to force data fetch AND update the cache with new data ... while 'x-apicache-bypass' completely bypasses the apicache middleware.