-
Notifications
You must be signed in to change notification settings - Fork 449
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Precondition failed" should provide more info #1133
Comments
Makes sense, will add some log statements |
@htgoebel - log statements added, but what is expected as error message (content/format)? Is a client able to display it? |
closing now as implemented in log and unclear how to display error message to client in which format. As support is needed for the 2nd one has to create a PR in case. |
Thanks for fixing.
Instead of returning
If you like the idea, I will provide a pull-request which implements a wrapper creating the response (depending on whether there
Clients would show it in the error log at least. |
PR is welcome, question is what should be disclosed? Case 1 Case 2 Case 3 Anyhow, user can only resync collection and try to update then what is still existing. |
I just spent more then one hour tracking down a "Precondition failed" issue. The cause tracked down to "Creation asked but item found: item can't be replaced".
Expected behaviour
If "Precondition failed",
The text was updated successfully, but these errors were encountered: