Timeline for Why getrawtransaction returns an HTTP STATUS CODE 500 for not found transactions?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 18, 2017 at 16:06 | comment | added | Nick ODell | 1) Looks like JSON to me. What do you get? If you want something that usually doesn't change between versions, the JSON error code (the negative number) changes less often than the error message. 2) Hey, I didn't pick the status codes. Just be glad it's not error 418. | |
| May 18, 2017 at 6:45 | comment | added | knocte | 404 doesn't mean "method not found" but simply "not found". Method not found would actually be better mapped to 400 "bad request" | |
| May 18, 2017 at 6:45 | comment | added | knocte | This is the problem I'm mentioning, the error response is not json and has even changed across versions: github.com/bitcoin/bitcoin/commit/… thus, one cannot distinguish between an error state of the server and the server claiming that the tx doesn't exist. I disagree that 500 should be thrown here, because 5xx errors are "server errors" and it's not a server error, it's just a normal response. See en.wikipedia.org/wiki/… , querying about a non-existent transaction is not something "unexpected". | |
| May 18, 2017 at 6:25 | history | answered | Nick ODell | CC BY-SA 3.0 |