HTTP cache support for the QUERY method (RFC 10008)#852
Open
hunghhdev wants to merge 1 commit into
Open
Conversation
Member
|
@hunghhdev Awesome! Out of curiosity is this effort coordinated with the original author of #840 or is it purely coincidental? Please note there is #850 that still needs to land that improves the process of cache key generation. Overall looks very good. |
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
2 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.
Follow-up to #840. The caching layer can now store and serve responses to
QUERYrequests: cache keys incorporate a digest of the request content and content type, and both classic and async interceptors bufferQUERYbodies instead of bypassing the cache. Anything that cannot be buffered safely still falls back to direct execution.