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

[Greg Wilkins <[e-mail]>]

Martin,

You are correct that it is not an extra round trip.  But I do not
think it is a good solution to send a complete HTTP message PLUS extra
stuff in the request.

If the handshake is legal HTTP, the server should be able to rejects
the websocket upgrade without closing the connection.  This would
allow the connection to remain in the browsers pool of connections and
avoid an extra round trip to establish another connection if the
application falls back to non-websocket transports.

Sending extra stuff after the response is OK.

cheers







On 7 July 2010 15:23, Thomson, Martin <[e-mail]> 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.
> _______________________________________________
> hybi mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/hybi
>