I hope this message finds you well. I am a user of your excellent open-source software jellyfin-android and I would like to request a new feature that I believe would greatly enhance the user experience.
Currently, when the login URL returns an HTTP status code between 301 and 307, the software does not follow the redirect and instead treats it as an error. I would like to propose that the software be modified to follow the redirect and use the URL specified in the Location header as the final login URL.
This feature would be particularly useful in scenarios where the login URL is subject to change due to server-side redirects or load balancing. By following the redirect, the software can ensure that the user is always directed to the correct login page, even if the original URL is no longer valid.
Here is a possible implementation approach：
When the login URL returns an HTTP status code between 301 and 307, the software checks the Location header for a valid URL.
If a valid URL is found, the software redirects the user to the new URL and continues with the login process.
If no valid URL is found, the software treats the response as an error and displays an error message to the user.
I believe this feature would be a valuable addition to the software and would greatly improve the user experience. I would be happy to provide any further information or assistance if needed.
Dear jellyfin,
I hope this message finds you well. I am a user of your excellent open-source software jellyfin-android and I would like to request a new feature that I believe would greatly enhance the user experience.
Currently, when the login URL returns an HTTP status code between 301 and 307, the software does not follow the redirect and instead treats it as an error. I would like to propose that the software be modified to follow the redirect and use the URL specified in the Location header as the final login URL.
This feature would be particularly useful in scenarios where the login URL is subject to change due to server-side redirects or load balancing. By following the redirect, the software can ensure that the user is always directed to the correct login page, even if the original URL is no longer valid.
Here is a possible implementation approach：
When the login URL returns an HTTP status code between 301 and 307, the software checks the Location header for a valid URL. If a valid URL is found, the software redirects the user to the new URL and continues with the login process. If no valid URL is found, the software treats the response as an error and displays an error message to the user. I believe this feature would be a valuable addition to the software and would greatly improve the user experience. I would be happy to provide any further information or assistance if needed.
Thank you for considering my request!
Best regards