Raise blacklist error on 403s #419
Open
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
If Travis API returns a 403 when the `Authorization` header is not set, raise an Error about blacklisting, not a NotLoggedIn exception.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
According to @rkh on issue #315, the Travis API will return a 403 if the "quite aggressive" auto-blocking bot blacklists your IP address. This PR raises an appropriate Error, not a NotLoggedIn exception, if Travis API returns a 403 when the
Authorizationheader is not set. I'm not sure if this is totally correct, though: ideally, the API would return a unique status code, like 503 Service Unavailable with a hugeRetry-After, so we could be absolutely sure. If we can do that, I'll update this PR accordingly.