Re: [hybi] #4: handshake does not work properly with HTTP reverse proxy.

[Willy Tarreau <[e-mail]>]

On Thu, Sep 02, 2010 at 02:31:45AM -0400, John Tamplin wrote:
> On Thu, Sep 2, 2010 at 2:11 AM, Willy Tarreau <[e-mail]> wrote:
> 
> > However I think that we should discuss this on the list once the new
> > framing
> > is agreed upon : instead of having both the client and the server implement
> > a specific case for something barely looking like some data can flow, we
> > can
> > as well send a real WS frame and expect a real one in return (eg:
> > ping+pong).
> > It would then be the real opening handshake which might be used later when
> > the protocol evolves to other non-HTTP transport methods. HTTP would then
> > be
> > just for connection establishment up to, but not including the WS
> > handshake.
> >
> 
> If we were going to have WebSocket frames exchanged for negotiation, I would
> prefer to define something specifically for it rather than overloading
> ping/pong.  If we add a separate control frame opcode, the extra cost would
> be negligible.

yes, that's a possibility too and it could be used to exchange some
required metadata that we don't want to put in headers or that could
not be transported by TLS.

Willy