When receiving a 401 HTTP response during the WebSocket handshake, Chrome will attempt to continue authentication on the same socket. Windows HTTP authentication usually requires a single connection to be reused for authentication to succeed. Until now, Chrome has always closed the connection on a 401 status response, so Windows authentication has not worked. Windows authentication support is mostly useful in enterprise environments where single-sign-on is used.

Specification

Editor's draft

Status in Chromium

Blink>Network>WebSockets


Enabled by default (tracking bug) in:

  • Chrome for desktop release 70
  • Chrome for Android release 70

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • Shipped/Shipping
  • Shipped/Shipping
  • No signal
  • Strongly positive

Owner

Last updated on 2020-11-09