When issuing an RPC for walletpassphrase, the following error is returned:
{"result":null,"error":{"code":-19,"message":"Wallet file not specified (must request wallet RPC through /wallet/<filename> uri-path)."},"id":0}
Documentation from here: https://bitcoincore.org/en/doc/0.20.0/rpc/wallet/walletpassphrase/ states sample call looks like this: _As a JSON-RPC call
curl --user myusername --data-binary '{"jsonrpc": "1.0", "id": "curltest", "method": "walletpassphrase", "params": ["my pass phrase", 60]}' -H 'content-type: text/plain;' http://127.0.0.1:8332/_ (e.g. no /wallet/<filename> in the RPC)
Further, my issue stems from wallet names with embedded spaces, for example "encrypted with space". QT allows for the creation of wallet names with spaces (and other characters), which are not valid in a URI, at least as plain text.
The CLI functions as expected when issued with the rpcwallet parameter, and allows for spaces because the wallet name is enclosed in double quotes.
At a minimum the docs should reflect the proper usage of the RPC call, however its unclear how support for wallet names with internal spaces would be supported at all given the current design. A better design would be to add the wallet name as a parameter in the array to avoid using different URIs which is inconsistent with the usage of all other RPCs in core.
BTC 0.21
