diff options
author | Matthew Zipkin <pinheadmz@gmail.com> | 2024-06-05 11:00:11 -0400 |
---|---|---|
committer | Matthew Zipkin <pinheadmz@gmail.com> | 2024-06-07 09:26:50 -0400 |
commit | 0ead71df8c83a2f9eae1220544ec84dcf38a0326 (patch) | |
tree | 7e6e3e09d1761e793c5760d9b5aee7ec8567fe02 /doc/release-notes-27101.md | |
parent | 1040a1fc807ed984020eeaa6e90b5bf070b61b05 (diff) | |
download | bitcoin-0ead71df8c83a2f9eae1220544ec84dcf38a0326.tar.xz |
doc: update and link for JSON-RPC 2.0
Diffstat (limited to 'doc/release-notes-27101.md')
-rw-r--r-- | doc/release-notes-27101.md | 7 |
1 files changed, 2 insertions, 5 deletions
diff --git a/doc/release-notes-27101.md b/doc/release-notes-27101.md index 8775b59c00..7ce1e9a8c1 100644 --- a/doc/release-notes-27101.md +++ b/doc/release-notes-27101.md @@ -2,8 +2,5 @@ JSON-RPC -------- The JSON-RPC server now recognizes JSON-RPC 2.0 requests and responds with -strict adherence to the specification (https://www.jsonrpc.org/specification): - -- Returning HTTP "204 No Content" responses to JSON-RPC 2.0 notifications instead of full responses. -- Returning HTTP "200 OK" responses in all other cases, rather than 404 responses for unknown methods, 500 responses for invalid parameters, etc. -- Returning either "result" fields or "error" fields in JSON-RPC responses, rather than returning both fields with one field set to null. +strict adherence to the [specification](https://www.jsonrpc.org/specification). +See [JSON-RPC-interface.md](/doc/JSON-RPC-interface.md#json-rpc-11-vs-20) for details.
\ No newline at end of file |