Re: [hybi] WebSocket -76 is incompatible with HTTP reverse proxies

[Willy Tarreau <[e-mail]>]

On Wed, Jul 07, 2010 at 01:23:22PM +0800, Thomson, Martin wrote:
> 
> > Content-length: 0 also makes sense but it means that the nonce will
> > be sent *after* the handshake, which means we'd have a second
> > round-trip. 
> 
> The round-trip thing is a fallacy.  Just as you can pipeline requests, so can you send extra handshakey parts after the headers.
> 
> Solution:  The handshake includes a complete HTTP message, PLUS extra stuff.  All of this is sent at once, but the HTTP stuff stops half way.
> 
> This is only true if the extra stuff is dependent on information from the peer, which is not the case in this scenario.

You're perfectly right Martin, this was a stupid comment of mine in fact.
The extra round-trip will only be between the reverse proxy and the server,
which is not a problem since both are supposed to be very close one to the
other. So, let's have content-length: 0 in both directions and have the
nonce transported *after* the handshake and tested by the client.

Willy