Since updating to 2.0.0.3530, I’ve noticed an issue with Sonarr’s rTorrent client integration. Sonarr appears to URL encode the category specified in the rTorrent download client option. For example, category ~/private/rtorrent/download/tv/ is transmitted as %7e%2fprivate%2frtorrent%2fdownload%2ftv%2f. This is an issue for users who have set up rTorrent to perform actions on torrents based on their category, in my example, torrents are automatically moved to the path specified in the category.
Note that this issue is not apparent from ruTorrent - the category is printed unescaped there. However, if you look at the category in rTorrent’s CLI, you’ll see the issue. You can do this by opening up rTorrent, selecting a torrent that was added by Sonarr, pressing Ctrl-X and typing:
A category is meant to be a text label, not a path, you can specify a directory in the Directory field.
rTorrent sends the category from its API as a URL encoded value, I would expect that it would handle a URL encoded value being sent when the label is set.
rTorrent’s wiki suggests using the category to store the path when managing multiple watch folders, and that’s why I am using it here. I’ve already worked around the issue by using the Directory field plus some additional smarts in the .rtorrent.rc to prevent rTorrent from moving the file on complete when Sonarr uploads a torrent via the API.
It appears rTorrent (0.9.4) does not handle a URL encoded value despite the API using them. For what it’s worth, this worked normally on Sonarr 2.0.0.3357 - I assume it’s this commit that changed this behaviour.