There is an abnormality when opening Overseer-related links in Homarr. about homarr HOT 4 CLOSED

Hi, Homarr is redirecting as expected. We use a simple a (aka. link) element with no unusual attributes. I have the same bug in my setup and this is almost certainly not an issue with Homarr. Please report this to the Overseerr / Jellyseerr developers and post the link here.

FYI @SeDemal

PS: You can briefly see that Homarr opens the correct URL when you look closely at the URL bar or record a video. Same is visible in the network analyzer

from homarr.

Hi, Homarr is redirecting as expected. We use a simple a (aka. link) element with no unusual attributes. I have the same bug in my setup and this is almost certainly not an issue with Homarr. Please report this to the Overseerr / Jellyseerr developers and post the link here.

FYI @SeDemal

PS: You can briefly see that Homarr opens the correct URL when you look closely at the URL bar or record a video. Same is visible in the network analyzer

https://github.com/sct/overseerr/issues/3716
It seems that this question indeed belongs to Overseerr. I found relevant content in the project's issue.

from homarr.

Thanks, will link this issue and close it as non completed sct/overseerr#3716

from homarr.

Hi, Homarr is redirecting as expected. We use a simple a (aka. link) element with no unusual attributes. I have the same bug in my setup and this is almost certainly not an issue with Homarr. Please report this to the Overseerr / Jellyseerr developers and post the link here.

FYI @SeDemal

PS: You can briefly see that Homarr opens the correct URL when you look closely at the URL bar or record a video. Same is visible in the network analyzer

I have discovered a perplexing reason.

I pinned the tabs of the Homarr app in Safari and opened an external link related to Overseerr from one of those tabs: http://instance/tv/0000. At this point, the bug of being redirected to the Overseerr login page no longer occurs.

By inspecting the network traffic, I observed that the GET request to http://instance/tv/0000 contained cookie information. Previously, this information did not exist. Instead, it was present in the subsequent GET request to http://instance/site.webmanifest. The GET request to http://instance/login occurred between these two requests.

from homarr.