fix: Corrects the order of caching + authorization middlewares #1661
+288
−2
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.
Resolves #1660
Before the change?
The HTTP caching doesn't have the Authorization header available to it, and therefore caches + returns values across user boundaries.
After the change?
The HTTP caching middleware happens after then authorization middleware, and therefore has the Authorization header and can cache requests per user.
Pull request checklist
Does this introduce a breaking change?
Please see our docs on breaking changes to help!