Bug: RPC returns "success" for non-existent hashes.
Posted: Tue Jan 08, 2013 6:31 pm
Running transmissioncli on version 2.03 (11030), upon sending the following RPC request:
where the hash "63c5d03c8111cf499d18c18d33e61c9b81d92270" does not exist in this Transmission, it responds with:
Similarly,
responds with:
In the RPC spec, 2.2.1 says that "A required "result" string whose value MUST be "success" on success, or an error string on failure.". No definition of "success" is provided, though I would deem this behaviour non-successful, as you can't verify or check progress on a torrent that doesn't exist, and an error string should be returned.
Recipe:
1. Set up transmissioncli 2.03 (11030) with RPC access.
2. Send aforementioned request string.
3. Recieve response, it is incorrect.
Thoughts?
Code: Select all
{"method":"torrent-verify","arguments":{"ids":["63c5d03c8111cf499d18c18d33e61c9b81d92270"]},"tag":4}Code: Select all
{"arguments":{},"result":"success","tag":4}Code: Select all
{"method":"torrent-get","arguments":{"ids":["63c5d03c8111cf499d18c18d33e61c9b81d92270"],"fields":["recheckProgress"]},"tag":8}Code: Select all
{"arguments":{"torrents":[]},"result":"success","tag":8}Recipe:
1. Set up transmissioncli 2.03 (11030) with RPC access.
2. Send aforementioned request string.
3. Recieve response, it is incorrect.
Thoughts?