BasicAuth not handled by Service Worker

[iamjrock]

Description

Many of us protect Jellyfin with an https proxy that supplies BasicAuth challenges.

With such a basic auth proxy (eg. Caddy) in front of Jellyfin, on an empty cache the BasicAuth challenge pops up.

However, upon revisiting the Jellyfin site later, the Jellyfin service worker has been installed in the browser and it mediates between the browser and the server. The service worker does not handle the BasicAuth 401 challenge and instead just returns the empty 401 content.

Version

1.7.0

Steps to Reproduce

See description.

Screenshots

No response

Logs

No response

Platform

desktop

Device

PC

Operating System

Windows 11

Browser

Firefox, Chrome

Additional Context

No response

Code of Conduct

• [X] I agree to follow Jellyseerr's Code of Conduct