-
Notifications
You must be signed in to change notification settings - Fork 581
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support draft-75 #6
Comments
Just tested with Chrome 14, Firefox 7, Safari 5.1 and IE 10. All seem to use draft-75 for secure WebSockets, and thus can't make secure connections to Fleck. However, plain-old-websockets with Fleck work for all of the mentioned browsers. |
That's odd. I understand that using SSL eliminates cache poisoning (a major pre-hixie07 concern), but 75 gives up support for other things like message segments and binary. I'll be taking a look at this today. |
Fixed the issue against Chrome, RequestParser was allowing incomplete requests to come through and spitting out an empty WebSocketHttpRequest. The HandlerFactory was then attempting to provide a handler based on the empty request; the default version from I'm having some issues getting secure websockets to work on Firefox, as it gets very unhappy about self-signed certificates. If you could re-attempt your cross-browser test against this latest commit and get back to me, that would be great. |
Not so sure this is worth it any longer. Safari seems to be the lowest using draft-76/hybi-00 which is supported by Fleck. I'll close this until someone has an issue. |
Draft 75 is still in use. It might be a good idea to include it.
The text was updated successfully, but these errors were encountered: