[1.x] Add X-Retry-After to /user/confirm-password/status response
#565
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
This would be useful for SPA application where we can register a timeout before checking the endpoint again. Signed-off-by: Mior Muhammad Zaki <[email protected]>
crynobone
force-pushed
the
password-status-retry-after
branch
from
7b5df9c to
f7deb20
Compare
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.
This would be useful for SPA application where we can register a timeout before checking the endpoint again.
Here, I chosen to use
X-Retry-Afterinstead of Retry-After since the documentation suggest the usage to be limited to301,429and503response status.