Catch and raise HTTP 403 Forbidden errors#958
Merged
Conversation
|
matches what i had tried in #936, much welcomed ! |
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
3 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.
It would have been easier to see the reason for recent failing CI tests (see #956) if an error had been raised when HTTP code 403 was returned.
As HTTP error code is a client error code, I added to the list with 400 and 401 (rather than the server error codes 5xx list).
See also #936.
Note, this could break existing workflows by raising a ServiceException - so comments/thoughts welcome.