kerryjiang/WebSocket4Net — pull request #11 by larskn (2014-06-06 12:41:07+00:00)
Title: Fixed two issues

1. When the socket was closed while connecting (meaning the connection establishment effectively failed but without an error), no event listener was called because OnClose does not fire when status is Connecting. This resulted in the client basically being in "limbo", because the connection failed but the application was not notified and is not able to react.
2. Commit 266f7dea588ab3ef18b1e0d5079351fcc67cf536 corrected the Origin header for hybi10, but since Rfc6455Processor inherits from DraftHybi10Processor it broke the Origin header for RFC 6455 at the same time. (in RFC 6455 its "Origin" again, not "Sec-WebSocket-Origin"). This causes problem when WebSocket server implementations try to access this (required) header field.