Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DuckieTV querying invalid Transmission RPC URL #1328

Open
talios opened this issue Sep 22, 2021 · 1 comment
Open

DuckieTV querying invalid Transmission RPC URL #1328

talios opened this issue Sep 22, 2021 · 1 comment

Comments

@talios
Copy link

talios commented Sep 22, 2021

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/

@garfield69
Copy link
Collaborator

thanks for reporting.
I'll take a look and see if we can add a template mask to the address field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants