Open
Conversation
|
@zaru can you please merge and release new version? This 406 error is really annoying for many people |
Contributor
|
This proposal is semantically wrong: you cannot catch a 406, which has a very specific meaning, and raise However I understand that the bug is caused by Microsoft. Is there at least a specific |
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.
According to documentation Microsoft servers don't send 429, but sometimes they start sending 406, which basically means "try again later" as I see it.
I'd rather receive
TooManyRequestserror instead ofNotAcceptable, 'cause it requires the same processing.As far as I'm concerned, other services do not send 406, so it should be OK.