j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMã<div class="post">I just submitted a patch to Satoshi to make bitcoin follow the <a href="http://groups.google.com/group/json-rpc/web/json-rpc-over-http">JSON RPC over HTTP spec,</a> and to use the standardized error codes from the JSON-RPC 1.1/2.0 specs.<br/><br/>If you talk directly to bitcoin via JSON-RPC calls, you might need to change your code to recognize the new HTTP status codes and the new format for the 'error' member of the JSON response. For example:<br/><br/>BEFORE, send {"id":"123", "method": "nosuchmethod", "params": [] } , get response:<br/><div class="codeheader">Code:</div><div class="code">HTTP/1.1 500 Internal Server Error<br/>...<br/><br/>{"result":null,"error":"Method not found.","id":"123"}</div>AFTER:<div class="codeheader">Code:</div><div class="code">HTTP/1.1 404 <br/>...<br/><br/>{"result":null,"error":{"code":-32601,"message":"Method not found"},"id":"123"}<br/></div><br/>I also removed the broken 'Batch' support, to simplify the code. I had JSON-RPC-2.0 batch support working properly, but backed those changes out because JSON-RPC 2.0 is way too cutting-edge for bitcoin to support right now (none of the JSON-RPC glue libraries support it yet, and the spec is still changing a bit).<br/></div> text/html
https://whatsonchain.com/tx/bd85949dbe2a5d77c062e04bfda7a0bd2be6c8d552ae8367109ad92c828beb35