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

> @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.

If I am understanding the situation correctly: as an author using fetch, I would expect to get a 401 Response object, with no user prompting ever. Then I could maybe cook up and supply an `Authorization` header. Possibly I would do that by asking the user (using a much nicer form than the browser one!) to enter a username and password; possibly I would use cookies; etc. etc.

I don't understand why anything else would be desirable.

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