Draft
Conversation
Author
|
I just figured out, that this breaks creating resources which do not yet exist. |
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
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.
Currently, the code only checks for 400 errors in which case an exception is raised.
When the HTTP token expires during a request though, the BigIP responds with a 401 error.
This leads to ugly error messages like this one, which does in no way indicate what's really going on:
With this patch exceptions are raise for 401 errors too and for all other possible HTTP errors (e.g. BigIP becoming unresponsive while being accessed via an HTTP proxy, which would result in a 503 error).
Error messages now mean something: