diff options
author | Ryan Ofsky <ryan@ofsky.org> | 2022-12-02 17:53:16 -0500 |
---|---|---|
committer | Ryan Ofsky <ryan@ofsky.org> | 2022-12-02 17:53:16 -0500 |
commit | 6bd1d20b8cf27aa72ec2907342787e6fc9f94c50 (patch) | |
tree | ae6a0867a99e33740aef9450cfdda75912c051cb /doc/release-notes-26628.md | |
parent | e2c3b18e671e347e422d696d1cbdd9f82b2ce468 (diff) | |
download | bitcoin-6bd1d20b8cf27aa72ec2907342787e6fc9f94c50.tar.xz |
rpc: Make it an error server-side to specify same named parameter multiple times
Specifying same named parameter multiple times is still allowed by bitcoin-cli.
The client implementation overwrites earlier option values with later ones
before sending to server. This is tested by interface_bitcoin_cli.py
Rationale for allowing client parameters to be specified multiple times in
bitcoin-cli is that this behavior has been supported for a long time, and that
when using the command line interactively, it can be convenient to override
earlier option values with new values without having to go back and remove the
old value.
But for the RPC server, there isn't really a good use-case for earlier values
to be discarded if multiple values are specified. JSON keys are generally
supposed to be unique and if they aren't it's probably an indication of some
problem generating the RPC request.
Diffstat (limited to 'doc/release-notes-26628.md')
-rw-r--r-- | doc/release-notes-26628.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/release-notes-26628.md b/doc/release-notes-26628.md new file mode 100644 index 0000000000..48a07c1e81 --- /dev/null +++ b/doc/release-notes-26628.md @@ -0,0 +1,4 @@ +JSON-RPC +--- + +The JSON-RPC server now rejects requests where a parameter is specified multiple times with the same name, instead of silently overwriting earlier parameter values with later ones. (#26628) |