pgriess node-websocket-client issues

pgriess / node-websocket-client

A Web Socket client for NodeJS

BSD 3-Clause "New" or "Revised" License

150 stars 68 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

WSS Support

#30 alissonpelizaro opened 5 years ago
0
`websocket` not found

#29 nitinsurana opened 7 years ago
0
http.createClient is not a function

#28 ghost opened 7 years ago
2
typo in usage

#27 mattiaswelander opened 8 years ago
0
Fix use of undefined variable in error message in websocket.js

#26 addrummond closed 6 years ago
0
The "sys" module is now called "util".

#25 takano32 closed 12 years ago
0
https support and basic authentication

#24 vukasin closed 3 years ago
0
Proper implementation of an auto-reconnect?

#23 ryonlife opened 12 years ago
0
[HTTP Parser] Parse error on https://myopenid.com

#22 nsigustavo opened 12 years ago
0
Combine Node0.6 fix from alaingilbert

#21 quangv opened 13 years ago
3
'sys' renamed to 'util' for node 0.6.1 silent warning fix

#20 quangv opened 13 years ago
7
Fix the lib for v0.5 and v0.6 of nodejs. It's also backward compatible with v0.4

#19 alaingilbert opened 13 years ago
2
Doesn't work with Node 0.6

#18 tristanz opened 13 years ago
1
npm repository tarball does not work with gnu-tar

#17 ddopson opened 13 years ago
0
hi^^ wss support?

#16 nanha opened 13 years ago
3
Latest release of nodejs (0.5.8) - Does not work at all

#15 alaingilbert opened 13 years ago
0
Lazily evaluate arguments to debug calls

#14 bwillard opened 13 years ago
0
Optimize debug() calls for performance boost

#13 pingdom-christian opened 13 years ago
1
Optimised send() and fixed up tests

#12 ThisIsMissEm closed 3 years ago
1
can't decode onmessage

#11 polidore opened 13 years ago
0
Expose underlying net.Stream

#10 rauchg opened 13 years ago
0
Update for http.Agent and npm > 1.0

#9 indexzero closed 12 years ago
1
Optional graceful close specified by WebSocket constructor

#8 pgriess opened 13 years ago
1
npm install websocket-client fails

#7 tehnorm closed 13 years ago
1
If close() isn't passed a timeout, finishClose is never called and the socket isn't cleaned up

#6 josephg closed 13 years ago
2
The host header of a HTTP request should include a port part if the port is not default (80)

#5 izuzak closed 13 years ago
4
Client should detect closing frame and close the connection (not crash)

#4 izuzak closed 13 years ago
6
Compatibility with SocketIO

#3 pclifford closed 14 years ago
1
Origin header required

#2 qrush closed 14 years ago
1
targetStart out of bounds [websocket.js:246]

#1 lgreenspan closed 14 years ago
3