Open dbackeus opened 10 years ago
Yes. This is intentional and due to a limitation. But it won't affect your in generally in development. And never affect to the production deployment.
Send me a PR.
Arunoda Susiripala I curate Meteor Weekly - Check it out! http://meteorhacks.com/meteor-weekly/?utm_source=email-footer&utm_medium=email&utm_campaign=meteorweekly
On Tue, Jul 29, 2014 at 2:26 PM, David Backeus notifications@github.com wrote:
I get this error in my JS console when opening my Meteor app using the proxy:
WebSocket connection to 'ws://localhost:3030/sockjs/788/lnfxrvrn/websocket' failed: Connection closed before receiving a handshake response
It then falls back to regular http calls.
If this is intentional it should be added to the readme.
— Reply to this email directly or view it on GitHub https://github.com/arunoda/meteor-ddp-analyzer/issues/7.
What is the limitation you mentioned? Using localhost and not a proper domain?
Actually DDP analyzer is a customized SockJS proxy. I have done some hacks in order to get it working. But it prevents WebSockets. It can be fixed. But that's not a high priority at the moment.
On Tuesday, August 12, 2014, David Backeus notifications@github.com wrote:
What is the limitation you mentioned? Using localhost and not a proper domain?
— Reply to this email directly or view it on GitHub https://github.com/arunoda/meteor-ddp-analyzer/issues/7#issuecomment-51901475 .
Arunoda Susiripala
@arunoda http://twitter.com/arunoda http://gplus.to/arunodahttps://github.com/arunoda http://www.linkedin.com/in/arunoda
PR updating the README as a first step: https://github.com/arunoda/meteor-ddp-analyzer/pull/8
I get this error in my JS console when opening my Meteor app using the proxy:
It then falls back to regular http calls.
If this is intentional it should be added to the readme.