Re: [hybi] Final HTTP responses and WebSocket handshake

Agreed.

I would much prefer to see full HTTP compatibility before the handshake
completes with a 101 response.

John.

On Thu, Feb 10, 2011 at 5:48 PM, Greg Wilkins <gregw@webtide.com> wrote:

> On 11 February 2011 12:40,  <Yutaka_Takeda@playstation.sony.com> wrote:
> >
> > o  Cannot get full benefit out of HTTP protocol during the handshake as
> it
> > does not expect a final response:
> >   For example:
> >    - Can not redirect WebSocket handshake to another server (for load
> > balancing, fail-over, etc.)
> >    - Can not perform user authentication (Basic, Digest, etc.) during the
> > handshake.
> >    - Similarly, 407 authentication cannot be forced by the server.
>
> +1
>
> In the ancient history of this list, I have long argued for exactly this.
>
> Apparently there are some security concerns about browser redirection,
> which I never really understood... and even if there are, I don't see
> the reason that the protocol should deny the use of non 101 handshake
> responses to all clients.  I think the protocol should allow arbitrary
> response codes (because it can't actually prevent them being sent by
> non WS servers anyway), and then individual clients can decide which
> responses they will handle (which may be better discuss in the
> appropriate HTML 5 forums regarding the specific websocket API).
>
> cheers
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>

-- 
>|< Kaazing Corporation >|<
John Fallows | CTO | +1.650.960.8148
444 Castro St, Suite 1100 | Mountain View, CA 94041, USA