Ian Hickson wrote: > I disagree that the current handshake isn't like HTTP enough, though. The > request is fully HTTP-compliant. What value would there be in relaxing the > rules on what WebSocket clients should send in the request? I don't > understand the real-world case you are concerned about. What about a load balancer in front of the server that inserts a cookie or X-Forwarded-For header into all HTTP requests that it forwards. This will probably be harmless with regards to the subsequent WS connection, but it will break the handshake so there will not be a subsequent WS connection. regards
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.