feat: make POST requests cacheable #24
Merged
Conversation
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
This was referenced Jan 6, 2022
Owner
dwrBad
force-pushed
the
main
branch
2 times, most recently
from
b2bc1e5 to
6dd1af3
Compare
Contributor
Author
|
Hi @StarpTech |
|
+1 on this PR. LGTM. |
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.
This PR is related to #19
It makes POST requests cacheable. Default behavior will still be the same – only GET requests will be cached. But you may manually overwrite
isRequestCacheable()to define a default behaviour. Additionaly you should/must overwriteonCacheKeyCalculationto define an adequate caching key (including the body for example).