Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[HTTP API] be more precise about the cause of an error #664

Closed
sbellem opened this issue Oct 5, 2016 · 2 comments
Closed

[HTTP API] be more precise about the cause of an error #664

sbellem opened this issue Oct 5, 2016 · 2 comments
Assignees
@sbellem

Comments

@sbellem
Copy link
Contributor

sbellem commented Oct 5, 2016

Currently, it is possible to get 400 errors for various reasons (input transaction not found, double spend, invalid signature, etc), but an API user, will only receive an 'Inavlid transaction' message.

This issue proposes to pass on the exact reason for an invalid transaction as part of the response.
@sbellem sbellem self-assigned this Oct 5, 2016
@sbellem sbellem changed the title server api: be more precise about the cause of an error [HTTP API] be more precise about the cause of an error Oct 14, 2016
@sbellem sbellem mentioned this issue Dec 8, 2016
Merged
@ttmc
Copy link
Contributor

ttmc commented Dec 10, 2016

@sbellem Do you think that pull request #916 resolved this issue, or is there still more to do?

@sbellem
Copy link
Contributor Author

sbellem commented Dec 10, 2016

@ttmc there could perhaps be more to do but we can close the issue and re-open as needed.

@sbellem sbellem closed this as completed Dec 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sbellem sbellem

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sbellem @ttmc