[resent from whatwg at whatwg.org, with slight additions here] Hi, so I was reading the web sockets spec as well as a Firefox patch to implement it. Is it intentional that it is impossible to implement this spec over an existing HTTP stack, as currently specified? In particular, due to the strict requirements on the headers to send, it seems like you can't really implement it with an existing HTTP stack. On the other hand, you really do want to reuse your HTTP implementation, because otherwise you have to reimplement all your HTTP proxy authentication, including NTLM, GSSAPI, etc. Obviously another problem would be that the actual bidirectional communication might be hard to fit into your HTTP implementation, but that might be easier to work around. I'll note that the implementation on Chromium trunk skips authentication completely at the moment (http://src.chromium.org/viewvc/chrome/trunk/src/net/websockets/websocket.cc?view=markup, search for 407) Do you as the spec authors have any thoughts on this? -christian
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.