Description:

When configuring the auth.server URL with a trailing slash (e.g., https://example.com/), API calls generate malformed URLs containing double slashes (//). This breaks operations like fetching thumbnails, where the resulting URLs are incorrect and fail to load.

Steps to Reproduce:

1. Configure auth.server with a trailing slash (https://example.com/).
2. Fetch media thumbnails or other API resources.
3. Observe the generated URL contains a double slash, e.g., https://example.com//Items/....

Expected Behavior: The generated URL should be correctly formatted as https://example.com/Items/..., without double slashes.

Proposed Fix: The issue is resolved by sanitizing both the base URL and the handler in the jellyfin_url function. The updated implementation is as follows:

def jellyfin_url(client, handler):
    base_url = client.config.data['auth.server'].rstrip('/')
    return f"{base_url}/{handler.lstrip('/')}"

This ensures:

• No trailing slash in the base URL.
• No leading slash in the handler.
• The final URL is properly constructed with exactly one / between components.

Additional Context: The fix ensures robust URL generation regardless of user configuration.