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

> So, I would not expect a prompt when you hand the response to the service worker, but rather when the service worker hands the response to the browsing context navigating. Or is that what you meant?

Yes, that's what I meant. Currently we hand the response back to the Service Worker which hands it to the navigating browsing context and we never show a prompt. What I'd like to do is:
1.) Hand a network error to the Service Worker, who can hand that or a cached response to the navigating browsing context
2.) Show a prompt when the navigation commits, if it's the network error

> (Another somewhat-related question I have is how you handle cross-origin nested browsing contexts navigating to such responses, but maybe we should tackle that separately.)

We'd really like to get rid of prompts from cross-origin subresources and nested browsing contexts altogether, but not sure if we'll be able to do that in the foreseeable future (https://bugs.chromium.org/p/chromium/issues/detail?id=400380#c24). In the meantime, we only use the interstitial for top-frame navigations, not nested browsing contexts, since the latter usually already has the ability to spoof content in the context of the parent page.

-- 
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-755464809