Skip to content
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

ws example server and FF #133

Open
nickdesaulniers opened this issue Oct 26, 2015 · 4 comments
Open

ws example server and FF #133

nickdesaulniers opened this issue Oct 26, 2015 · 4 comments

Comments

@nickdesaulniers
Copy link
Owner

https://bugzilla.mozilla.org/show_bug.cgi?id=1216237

not sure yet if this is upstream or not.

@reqshark
Copy link
Collaborator

oh based on the comment on the bug maybe we need to be handling an upgrade request header on that node server. all i was doing there was piping the readstream to the response stream without opts

@reqshark
Copy link
Collaborator

reqshark commented Nov 4, 2015

handling an upgrade request header on that node server

no dice.

we can listen for the require('http').createServer()'s 'upgrade' event, but it never hits port 3000, since upgrade request fires from WebSocket constructor directed to pair socket on :7789

@reqshark
Copy link
Collaborator

looks like a fix is in the works upstream nanomsg/nanomsg#783

@nickdesaulniers
Copy link
Owner Author

We should test if this is obsolete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants