Re: [whatwg/fetch] Allow more flexibility in how 401s/407s are handled? (#1132)

How should service workers handle the network error resulting from the browser not prompting the user for username and password?

I'm affected by the bug in chrome, my page uses a service worker and is protected with Basic auth. The page can not load in chrome because all service worker requests are Unauthorized (401) and even when reloading the page chrome does not prompt for the basic auth credentials. The only workaround currently is to open a protected resource in a new tab which is not cached in the service worker to trigger the auth prompt and the reload the page with the service worker.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1132#issuecomment-752736318