Stop saying HTTP authentication over WebSocket is disallowed

Closes #565. Follow-up: #766.

Author: ricea

fetch.bs

@@ -6307,12 +6307,12 @@ therefore not shareable, a WebSocket connection is very close to identical to an
 <p><dfn>Fail the WebSocket connection</dfn> and <dfn>the WebSocket connection is established</dfn>
 are defined by The WebSocket Protocol. [[!WSP]]
 
-<p class=warning>The reason redirects are not followed, HTTP authentication will not function, and
-this handshake is generally restricted is because that could introduce serious security problems in
-a web browser context. For example, consider a host with a WebSocket server at one path and an open
-HTTP redirector at another. Suddenly, any script that can be given a particular WebSocket URL can be
-tricked into communicating to (and potentially sharing secrets with) any host on the internet, even
-if the script checks that the URL has the right hostname.
+<p class=warning>The reason redirects are not followed and this handshake is generally restricted is
+because it could introduce serious security problems in a web browser context. For example, consider
+a host with a WebSocket server at one path and an open HTTP redirector at another. Suddenly, any
+script that can be given a particular WebSocket URL can be tricked into communicating to (and
+potentially sharing secrets with) any host on the internet, even if the script checks that the URL
+has the right hostname.
 <!-- https://www.ietf.org/mail-archive/web/hybi/current/msg06951.html -->