[Webkit-unassigned] [Bug 80362] WebSocket: Client does not support 401 Unauthorized response.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=80362


Yuta Kitamura <yutak at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |ian at hixie.ch
     Ever Confirmed|0                           |1




--- Comment #1 from Yuta Kitamura <yutak at chromium.org>  2012-03-07 15:16:36 PST ---
We should do this, but how to implement this does not sound obvious to me.

By the way, WebSocket API spec has the following sentence:

    http://www.w3.org/TR/websockets/

    When the user agent validates the server's response during the "establish a 
    WebSocket connection" algorithm, if the status code received from the server 
    is not 101 (e.g. it is a redirect), the user agent must fail the websocket 
    connection.

The wording "not 101 (e.g. it is a redirect)" is a bit vague and there can be two understandings:
(1) the user agent must not perform redirection but must handle the other non-101 HTTP codes as it does in HTTP.
(2) the user agent must fail the WebSocket connection if the status code is not 101.

(2) is against RFC6455 so I assume (1) is right. Hixie, what do you think?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.