websockets/ws issues and pull requests

#2079 - Support Windows named pipes

Pull Request - State: closed - Opened by lpinca over 2 years ago - 2 comments

#2078 - useing localhost in url is not properly working

Issue - State: closed - Opened by mathe42 over 2 years ago - 2 comments

#2077 - In docs remove Object as a data type for send

Pull Request - State: closed - Opened by DLiblik over 2 years ago - 2 comments

#2076 - websocket.send does not allow object but docs state that it does

Issue - State: closed - Opened by DLiblik over 2 years ago - 5 comments

#2075 - Add named pipe support for Windows

Pull Request - State: closed - Opened by jacksteamdev over 2 years ago - 2 comments

#2074 - Question: Set headers for handshake

Issue - State: closed - Opened by MijikHna over 2 years ago - 2 comments

#2067 - Made "Simple Server" more complete and at the top

Pull Request - State: closed - Opened by SephReed over 2 years ago - 5 comments

#2059 - WSS not working on self-signed certificate (localhost)

Issue - State: closed - Opened by cbeltrangomez84 over 2 years ago - 5 comments

#2053 - Adding custom headers to HTTP Upgrade response

Issue - State: closed - Opened by bahamut657 over 2 years ago - 4 comments

#2050 - Please delete wiki pages related to automatic reconnection.

Issue - State: closed - Opened by BlackGlory over 2 years ago - 86 comments

#2041 - Help with URL on client side

Issue - State: closed - Opened by carlosveny almost 3 years ago - 5 comments

#2040 - How to reconnect automatically if websocket is closed?

Issue - State: closed - Opened by esuarezz almost 3 years ago - 3 comments

#2032 - Library has unexpected behavior in esm Node runtimes

Issue - State: closed - Opened by nopeless almost 3 years ago - 7 comments

#2022 - Suspected memory leak in send function

Issue - State: closed - Opened by HandsomeTea almost 3 years ago - 6 comments

#2021 - Syntax error

Issue - State: closed - Opened by JarZem almost 3 years ago - 3 comments

#1925 - Connect to websocket under cloudflare causes 403 forbidden error

Issue - State: closed - Opened by car1ot over 3 years ago - 19 comments

#1922 - ERROR Invalid WebSocket frame: invalid status code 22373

Issue - State: closed - Opened by arpowers over 3 years ago - 15 comments

#1910 - minor jsdoc improvements

Pull Request - State: closed - Opened by jimmywarting over 3 years ago - 2 comments

#1862 - Error: Server sent no subprotocol

Issue - State: closed - Opened by VidarHUN almost 4 years ago - 5 comments

#1825 - Server crashes with Invalid WebSocket frame

Issue - State: closed - Opened by pimvanderheijden about 4 years ago - 7 comments

#1818 - Use Node.js 15 native `EventTarget` object

Issue - State: open - Opened by piranna over 4 years ago - 47 comments

#1812 - Incompatibility between documentation and Typescript

Issue - State: closed - Opened by Don2Quixote over 4 years ago - 4 comments

#1745 - Can't send an error code or message when rejecting a connection due to auth failure

Issue - State: closed - Opened by pierznj almost 5 years ago - 10 comments

#1740 - How do I send an array of string ?

Issue - State: closed - Opened by qiulang almost 5 years ago - 2 comments

#1643 - Over wss the bufferedAmount is high and ws._socket.on('drain') never fires

Issue - State: closed - Opened by aeroxy over 5 years ago - 5 comments

#1639 - try catch does not actually catch

Issue - State: closed - Opened by bdotsamir over 5 years ago - 3 comments

#1574 - handshakeTimeout error code

Issue - State: closed - Opened by WuerfelDev over 5 years ago - 13 comments

#1540 - Error line 16 in /ws/lib/websocket.js

Issue - State: closed - Opened by LightBurdenOfficial almost 6 years ago - 3 comments

#1538 - WebSocket.Server is not a constructor

Issue - State: closed - Opened by pyeongoh almost 6 years ago - 24 comments

#1537 - WebSocket connection to 'ws://localhost:8000/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED

Issue - State: closed - Opened by DQ318 almost 6 years ago - 26 comments

#1517 - How to extend interface WebSocket with typescript?

Issue - State: closed - Opened by budarin almost 6 years ago - 25 comments

#1458 - WebSocket over HTTP2

Issue - State: open - Opened by rahbari over 6 years ago - 28 comments

#1433 - self signed certificate in certificate chain err

Issue - State: closed - Opened by LiranBratk over 6 years ago - 4 comments

#1426 - ECONNREFUSED throws a fatal exception

Issue - State: closed - Opened by artus9033 over 6 years ago - 4 comments

#1388 - How to get the specified websocket connection object.

Issue - State: closed - Opened by acexy over 6 years ago - 5 comments

#1369 - Zlib compression needs to be sync

Issue - State: open - Opened by ghost almost 7 years ago - 48 comments
Labels: discussion

#1354 - Websocket RangeError: Invalid WebSocket frame: RSV2 and RSV3 must be clear

Issue - State: closed - Opened by ztnark almost 7 years ago - 29 comments

#1353 - Supporting multiple instances of WS on a single HTTP server.

Issue - State: closed - Opened by sysaxis almost 7 years ago - 12 comments

#1315 - Invalid WebSocket frame

Issue - State: closed - Opened by imbundle almost 7 years ago - 8 comments

#1308 - Saving reference to ws

Issue - State: closed - Opened by basitsattar about 7 years ago - 7 comments

#1276 - set localAddress param not working

Issue - State: closed - Opened by ztiandan about 7 years ago - 15 comments

#1142 - doc clarification between ws.close() and ws.terminate()

Issue - State: closed - Opened by xileftenurb over 7 years ago - 17 comments

#1140 - Error: RSV1 must be clear

Issue - State: closed - Opened by wyzxxx123 over 7 years ago - 22 comments

#1135 - Ws with ssl

Issue - State: closed - Opened by sherikapotein over 7 years ago - 9 comments

#1126 - Module not found Warning when using ws in a webpack bundle

Issue - State: closed - Opened by crazyyi over 7 years ago - 13 comments

#1102 - ws.send method should support objects too

Issue - State: closed - Opened by ZaDarkSide almost 8 years ago - 9 comments

#1096 - I don't receive any errors when sending a message to a client.

Issue - State: closed - Opened by Valen558 almost 8 years ago - 8 comments

#1093 - Error: unexpected server response (200)

Issue - State: closed - Opened by mcordingley almost 8 years ago - 21 comments

#1087 - Get total number of connected clients on each new connection

Issue - State: closed - Opened by nodesocket almost 8 years ago - 5 comments

#979 - wss: Error during WebSocket handshake: Unexpected response code: 200

Issue - State: closed - Opened by Ratismal about 8 years ago - 32 comments

#977 - How do we enable ping/pong?

Issue - State: closed - Opened by john-doherty about 8 years ago - 9 comments
Labels: question

#893 - Websockets not working with HTTPS in an Apache Proxy (302 error?)

Issue - State: closed - Opened by DigitalLeaves over 8 years ago - 19 comments

#859 - unique identifier for each client request to websocket server

Issue - State: closed - Opened by altanai over 8 years ago - 19 comments

#659 - Dependencies bufferutil and utf-8-validate are listed as devDependencies

Issue - State: closed - Opened by TheLudd about 9 years ago - 13 comments

#542 - Is the order of messages guaranteed?

Issue - State: closed - Opened by bitliner over 9 years ago - 4 comments

#476 - WS and Node.js Cluster

Issue - State: closed - Opened by RWander almost 10 years ago - 21 comments

#473 - How to set initially cookies to a websocket client

Issue - State: closed - Opened by caub almost 10 years ago - 13 comments

#377 - Pass verifyClient result to `connection` event

Issue - State: open - Opened by pwnall over 10 years ago - 72 comments

#154 - Passing a live socket to a child process

Issue - State: closed - Opened by geoffreyd about 12 years ago - 13 comments

GitHub / websockets/ws issues and pull requests