Re: [hybi] WebSocket feedback

[Vladimir Katardjiev <[e-mail]>]

Heya Greg,

> GET's can have content.  It's just the browsers mostly don't send
> content with GETs.

Damn. I've been mired in REST stuff for so long, I could've sworn GETs shouldn't contain any body. You're correct, of course. Still, I do believe in this case it's not intended as an entity body, so not including Content-Length and Content-Type implies there is none (and is a valid way to send a request).

Again, I think the intention is to break the request if an intermediary doesn't handle WebSockets so sending the first WebSocket message as an entity body is probably not the desired effect.

> The server needs to consider the bytes of content before formulating
> the accepting the upgrade request and sending the 101 response, so
> it can't be considered as data in the stream after the 101.

Unless I'm reading it completely wrong, the contents of the 101 handshake (since it has no content-length) can and are constructed purely from the headers. The challenge response contains data from both headers and the 8-byte challenge that comes later, but it's fine to do it. The steps of the algorithm could be reordered with no change of the output so what we call it is a matter of interpretation. Po-tay-to, poh-ta-to.

Vladimir