Change in /command/download response since 3.3.12? (Sonarr broken)

[Arathen]

Has something changed in the way that qBt responds to a /command/download API request since 3.3.12 by any chance? Whilst 3.3.12 works fine, since then when Sonarr sends a magnet link to qBt using the download API there is some unexpected behaviour in Sonarr. It looks like Sonarr is expected a JSON response from qBt, but is actually just getting an "Ok." string back, which causes Sonarr to believe the handoff has been unsuccessful.

Sending torrents via the /command/upload API call still works fine.

I've kicked off a conversation on the Sonarr forums here https://forums.sonarr.tv/t/sonarr-doesnt-send-label-category-to-qbittorrent-for-magnets/14915 but that hasnt yielded a resolution as yet.

Cheers.

[Switeck]

These qBitTorrent issues might be related:

https://github.com/qbittorrent/qBittorrent/issues/7311
qBittorrent WebUI via IIS Reverse Proxy = 401 Blank Page

https://github.com/qbittorrent/qBittorrent/issues/6977
[BUG] WebUI API broken