You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see API requests being sent for http://USER:PASSWORD@HOST:9091/transmission:9091/transmission/rpc.
You can see that following the address, the port and path is just being appended to the Address.
After changing the address to simple being http:HOST - everything just worked. If the address is supposed to simply be protocol/hostname - some form of validation against putting the Transmission URL into the field, OR - the base path should be applied as a relative URL to that of the address/
The text was updated successfully, but these errors were encountered:
What build of DuckieTV are you using (Standlone / Chrome Extension (New Tab / Browser Action))
Standlaone: https://github.com/DuckieTV/Nightlies/releases/tag/nightly-202109072304
What version of DuckieTV are you using (Stable 1.1.x / Nightly yyyymmddHHMM)
Night as above: https://github.com/DuckieTV/Nightlies/releases/tag/nightly-202109072304
What is your Operating System (Windows, Mac, Linux, Android)
OS?X
Describe the problem you are having and steps to reproduce if available
Using Transmission as the torrent client with the following (redacted) settings:
I see API requests being sent for
http://USER:PASSWORD@HOST:9091/transmission:9091/transmission/rpc
.You can see that following the address, the port and path is just being appended to the Address.
After changing the address to simple being
http:HOST
- everything just worked. If the address is supposed to simply be protocol/hostname - some form of validation against putting the Transmission URL into the field, OR - the base path should be applied as a relative URL to that of the address/The text was updated successfully, but these errors were encountered: