Handling transmission host

[flying-sausages]

Currently, I can get the transmision connection going when I have https://domain.tld/transmission/rpc set as the server address. However when I click the TC icon, it brings me to that URL as well, which gives a 405.

Would it be possible to Allow setting the server address to just https://domain.tld/transmission/ and have TC handle torrent links to the /rpc, and the web interface to the /web though?

[Mika-]

You can just enter https://domain.tld/. The rest will be automatically appended.
This should be made more clear in settings.

[flying-sausages]

Thanks Mika, That works!.
However as my install is behind a reverse proxy, I would hope I'd be able to change the path as I'd want. Just by a coincidence, the https://domain.tld/transmission forwards to the 9091 port directly. If I point it to domain.tld, this coincidentally works. But if I'd like to use trnsmsn tor trans or something else for the reverse proxy's url, the whole thing would not work. It would be nice to be able to specify in advanced settings the full URL for the RPC and WEB endpoints. Somethginf for down the road, I think the amount of people with a similar use case would be quite low.

[Mika-]

Transmissions two level path is pretty much by specification. Other compliant clients (Vuze, Biglybt) also expose the same api with transmission prefix.