Tautulli connection fails with leading slash in base url

[jgillman]

Describe the bug
Tautulli connection fails when using a leading slash in base URL.

To Reproduce
(self explanatory, see screenshots)

Expected behavior
I would expect the connection to succeed with or without the leading slash in the base URL.

I'm not sure what the "standard" is but other similar services either automatically add/remove it or display an error. Overseerr, for example, says "URL base must have a leading slash" if it's not included to avoid confusion.

Screenshots

Fail with slash

Success without slash

Nginx logs

Device:

• OS: Slackware 15.0 x86_64 (docker container)
• Version 2.2.1

Additional context
Possibly related to #1305 ?

My screenshots show that I'm connecting with docker networking hostnames but I've confirmed that the behavior is the same if I use a local IP address or external domain.

[benscobie]

You're right it could be documented better. I would prefer a leading slash as well. At the very least Tautulli is consistent with the Radarr & Sonarr base URL settings. For now we could just add some help text alongside the input as we've got other higher priority things to work on. A PR is welcome.

[jgillman]

Thanks for the quick reply, @benscobie! Agreed that just adding some help text would be sufficient here. I'll see if I can get a PR together.

[ydkmlt84]

This is an easy documentation change for me. I will add it to the docs. Maintainerr UI will need a PR though. :)

[ydkmlt84]

Pushed the temp change to the develop branch.

Going forward, we would like to check for this on the server side and remove the slash if it is there. This will stay open until we implement that change.