Add JSON response for blocked account login #94
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
***Add JSON response for blocked account login in LogsOutBannedUser middleware
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 pull request includes changes to the
handlemethod in two middleware files,ForbidBannedUser.phpandLogsOutBannedUser.php. The changes add a check for whether the request expects a JSON response, and if so, it aborts the request with a 403 status code and a message indicating that the account is blocked.src/Http/Middleware/ForbidBannedUser.php: Added a check to see if the request expects a JSON response. If it does, the request is aborted with a 403 status code and an error message.src/Http/Middleware/LogsOutBannedUser.php: Similar to the change inForbidBannedUser.php, a check was added to see if the request expects a JSON response. If it does, the request is aborted with a 403 status code and an error message.