[whatwg/fetch] Investigate 401 handling for WebSocket (#766)

This is a follow-up to #565 and https://github.com/whatwg/fetch/pull/761#discussion_r195747178 in particular.

It'd be good to write more tests that cover the various scenarios:

1. Not authenticated, server replies with 401
2. Authenticated via `fetch()` with `Authorization` before opening the web socket connection.
3. 2, but server replies with a 401 anyway.
4. More?

Not sure all of those are easy to do in web-platform-tests given that authentication entries likely don't cross ports...

And review the algorithms in the standard again to ensure no prompting can take place ever (and maybe check again if implementations have the necessary bugs if they don't implement that).

-- 
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/766