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

I mean, in the spec, if the SW returns a response with an http url (it'd always be opaque) we tell the client to react to mixed content.

Actually, maybe "accepts mixed content" should be a request flag within fetch, then fetch can decide whether to just reject on an insecure response or trigger mixed content warnings.

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