Re: [hybi] Final HTTP responses and WebSocket handshake

[Greg Wilkins <[e-mail]>]

On 12 February 2011 10:26,  <[e-mail]> wrote:
>> In Section 1.3:
>> "Any status code other than 101 must be treated as a failure and the
>> websocket connection aborted."
>
> I agree, this needs to be fixed. In fact, any status code other than 101
> MUST be handled
> in a way that conforms with HTTP. (which is out of scope of this document).

I have a little concern with saying MUST be handled, as that could be
a little confusing. I don't think we can say that every client MUST
follow redirects, or MUST implement BASIC/DIGEST authentication.
Ignoring a redirect is still HTTP compliant behaviour.

I think we need to consider this in two parts: 1) what the handshake
can carry ; 2) what clients will commonly handle/respect.

For 1) I do not think their should be any restriction in the protocol
document about what the server can send back.  Any valid HTTP response
should be allowable.

For 2) I personally think that browsers at least should follow
redirects and support some common forms of authentication, but I
accept that is probably more an issue for the HTML5 community to
discuss rather than this WG.  But I certainly don't want to be telling
other non browser clients that they must follow redirects.

cheers