2 title: WebSockets Handshake non HTTP conforming?
11 While skimming through the new [HTML5 WebSocket draft](http://dev.w3.org/html5/websockets/),
12 I noticed the following exemplar HTTP message demonstrating the client message of a WebSocket handshake:
18 Sec-WebSocket-Key2: 12998 5 Y3 1 .P00
19 Sec-WebSocket-Protocol: sample
21 Sec-WebSocket-Key1: 4 @1 46546xW%0l 1 5
22 Origin: http://example.com
27 To me this looks non conforming to the [HTTP
28 spec](http://www.w3.org/Protocols/rfc2616/rfc2616.html) due to the lack of an
29 indicator that the request contains a message body.
31 Quoting [the 4th paragraph of section 4.3 of
32 RFC2616](http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.3):
34 > The **presence of a message-body** in a request **is signaled** by the
35 inclusion of a **Content-Length or Transfer-Encoding header** field in the
36 request's message-headers. A message-body MUST NOT be included in a request if
37 the specification of the request method (section 5.1.1) does not allow sending
38 an entity-body in requests. A server SHOULD read and forward a message-body on
39 any request; if the request method does not include defined semantics for an
40 entity-body, then the message-body SHOULD be ignored when handling the