Use 307 redirect when refreshing tokens in background to keep HTTP method #83
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.
Issue # (if available): fixes #82
Description of changes:
When redirecting to cognito, or we handle a request that's been redirected from cognito we likely want to try GET on the target since a) cognito expects it or b) if we've taken a detour to cognito the original method is lost anyway.
However, when we've refreshed tokens in the background and use a redirect response to the same url that was requested to set cookies we want the original request to be retried with the same method as it was originally made with, this way background POST/PUT/etc requests from web apps will not fail on the first try where tokens are refreshed
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.