QBittorrent Windows Paths with spaces not correctly decoded #4165

New issue

Closed

opened 2026-02-21 17:10:23 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-21 17:10:23 -05:00

Owner

Originally created by @qvazzler on GitHub (Apr 11, 2016).

https://github.com/Flexget/Flexget/issues/1013#issuecomment-208020061

The plugin isn't modifying the path any differently from other plugins, POST form data is encoded with '+' replacing spaces. It sounds like an issue on the qBittorrent side; they're probably not decoding the data correctly and assume no spaces in the path.

Is there any chance qBittorrent is not properly decoding in this scenario? Thanks for any advice.

Originally created by @qvazzler on GitHub (Apr 11, 2016). https://github.com/Flexget/Flexget/issues/1013#issuecomment-208020061 > The plugin isn't modifying the path any differently from other plugins, POST form data is encoded with '+' replacing spaces. It sounds like an issue on the qBittorrent side; they're probably not decoding the data correctly and assume no spaces in the path. Is there any chance qBittorrent is not properly decoding in this scenario? Thanks for any advice.

deekerman

2026-02-21 17:10:23 -05:00

closed this issue
added the
OS: Windows

WebUI
labels

deekerman commented

2026-02-21 17:10:28 -05:00

Author

Owner

@ngosang commented on GitHub (Apr 12, 2016):

qBittorrent API changed here => #4015 but we forgot to update the documentation. I updated it right now. I think you have to rewrite the qbittorrent plugin, sorry for that.
https://github.com/qbittorrent/qBittorrent/wiki/WebUI-API-Documentation#download-torrent-from-url

@ngosang commented on GitHub (Apr 12, 2016): qBittorrent API changed here => #4015 but we forgot to update the documentation. I updated it right now. I think you have to rewrite the qbittorrent plugin, sorry for that. https://github.com/qbittorrent/qBittorrent/wiki/WebUI-API-Documentation#download-torrent-from-url

deekerman commented

2026-02-21 17:10:29 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Apr 12, 2016):

So I should close this, right?

@sledgehammer999 commented on GitHub (Apr 12, 2016): So I should close this, right?

deekerman commented

2026-02-21 17:10:29 -05:00

Author

Owner

@ngosang commented on GitHub (Apr 15, 2016):