The problem with the ws module is it requires compiling native C++ code. Doing so is a bit problematic on Windows.
There's a few different potential ways of fixing this:
Remove use_ssl_strict and document it as such. Add a workaround note, which is pass a in a trusted certificate in ca property.
Issue/Pull request with faye-websockets to pass along the rejectUnauthorized property.
Issue/Pull request with ws to include precompiled binaries for the native extension, and switch back. This would be the most work but highest performance.
emgee3
commented
10 years ago
So with the switch from
wstofaye-websocketstheuse_ssl_strictoption no longer works. Lack of this is also probably the underlying cause for https://github.com/oortcloud/node-ddp-client/issues/20.faye-websocketsuses the underlying node TLS module for SSL but doesn't pass along therejectUnauthorizedproperty. See https://github.com/faye/faye-websocket-node/blob/master/lib/faye/websocket/client.js#L22-L34.The problem with the
wsmodule is it requires compiling native C++ code. Doing so is a bit problematic on Windows.There's a few different potential ways of fixing this:
use_ssl_strictand document it as such. Add a workaround note, which is pass a in a trusted certificate incaproperty.faye-websocketsto pass along therejectUnauthorizedproperty.wsto include precompiled binaries for the native extension, and switch back. This would be the most work but highest performance.