Re: [ServiceWorker] HTTP authentication and proxy authentication hook (#119)

@jakearchibald seems fine. Though the cache actually poses an interesting challenge. If you fetch a mixed content "no-cors" successfully and put it in the cache. And then close all tabs and come back, will the browser show mixed content? Where is that defined?

@sleevi the idea was for `fetch()` to have the minimum amount of magic by default. Network-spawn dialogs are pretty magic. I wonder what @domenic thinks. I guess I'm okay defaulting though if we have some kind of `{ client: null }` override (set all the time in dedicated/shared workers) if that is all that remains solving this puzzle.

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/119#issuecomment-118362069