Hey, thanks it helped to create a connection. But am not receiving any message from the server to thor. Its happening with wss connection only.I checked, to be sure that there is no error in the app deployment but I was receiving the response from server(using websocket.org echo test). Currently, Thor is showing message received=0 (whatever may be the message sent). Its working with non-ssl websocket connection but SSL one fails. Any suggestion?
On Saturday, 28 February 2015 09:44:21 UTC+5:30, 3rdEden wrote: > > So, that means you're using self signed certificates somewhere which are > unsave so node starts bitching about it. So you can use > > NODE_TLS_REJECT_UNAUTHORIZED=0 thor <things> > > To disable this node crap.. > > Op vrijdag 27 februari 2015 13:54:18 UTC-8 schreef Arundaya Mishra: >> >> I was using the thor to test one websocket application. It works great >> with ws but with wss its showing an error >> of unable_to_verify_leaf_signature. I hope the issue is with certificates >> thing but don't know how to resolve it. Any help on it. >> >> On Wednesday, 10 April 2013 17:15:00 UTC+5:30, 3rdEden wrote: >>> >>> Thor; https://github.com/observing/thor >>> >>> Thor is a WebSocket load generator tool that i've developed to >>> "accurately" test WebSocket servers and proxies. It's written in node and >>> uses the awesome `ws` module. Some of it's features are: >>> >>> >>> - Supports multiple urls >>> - Custom message generators >>> - Can write utf-8, binary and masked messages >>> - Different sizes of messages >>> - Custom concurrency and message counts >>> >>> >>> I've build this tool during my research on WebSocket capable proxies >>> like http-proxy from Nodejitsu, Nginx and HAProxy. The results of this >>> research is found at: https://github.com/observing/balancerbattle >>> >>> You can install thor from npm using: >>> >>> npm install -g thor >>> >>> >>> Would love to get some feedback on it and patches are welcomed! >>> >>> In addition to the release of thor i've also a written a nifty module >>> called: >>> >>> pre-commit; https://github.com/observing/pre-commit >>> >>> pre-commit automatically installs a pre-commit hook in your git >>> repository which will run your `npm test` before you commit your code. Now >>> you will never have broken test suites again ;) (unless you forcefully >>> ignore git hooks using git commit -n). In addition to running your `npm >>> test` it can also run all other scripts that you've specified in your >>> package.json. >>> >>> npm install pre-commit --save-dev >>> >>> >>> Anyways, check it out. It's a really simple project but can be really >>> helpful for larger module authors which want their contributors to always >>> run the tests when they commit/pull request something. >>> >> -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/3e6a25e2-65b7-4486-9773-afa41f5e3ab6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
