Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / websockets/ws issues and pull requests
#2180 - TypeError: Cannot read properties of undefined (reading 'mask')
Issue -
State: closed - Opened by rasp-pi-420 about 1 year ago
- 3 comments
#2179 - Bun compatibility
Issue -
State: closed - Opened by root-io about 1 year ago
- 1 comment
#2178 - Support for the oppurtunity to set frame headers before connection upgrade on the serverside
Pull Request -
State: closed - Opened by WarstekHUN about 1 year ago
- 5 comments
#2177 - How are we evaluating a handshake?
Issue -
State: closed - Opened by dav1app about 1 year ago
- 2 comments
#2176 - Cannot extend Server type
Issue -
State: closed - Opened by BCsabaEngine over 1 year ago
- 3 comments
#2175 - Error: WebSocket is not open: readyState 0 (CONNECTING) at onopen event.
Issue -
State: closed - Opened by ductridev over 1 year ago
- 14 comments
#2174 - [Question] Is it possible to skip compression/decompression of messages when sent or received by the websocket server/client
Issue -
State: closed - Opened by Sid200026 over 1 year ago
- 6 comments
#2173 - Can't resolve modules utf-8-validate and bufferutil in Next.js 13
Issue -
State: open - Opened by samuelnihoul over 1 year ago
- 2 comments
#2172 - Discrepancy between the documentation and implementation of the WebSocketServer.close method
Issue -
State: closed - Opened by schrodit over 1 year ago
- 2 comments
#2171 - WebSocketServer is not a constructor
Issue -
State: closed - Opened by mike-lischke over 1 year ago
- 7 comments
#2170 - App crashes for: RangeError: Invalid WebSocket frame: RSV2 and RSV3 must be clear
Issue -
State: closed - Opened by ile over 1 year ago
- 4 comments
#2169 - WebSocket Error: "Invalid WebSocket frame: RSV1 must be clear"
Issue -
State: closed - Opened by SimonVriesema over 1 year ago
- 9 comments
#2168 - No option to disable SSL validation for self-signed certificates?
Issue -
State: closed - Opened by jakemangansw over 1 year ago
- 2 comments
#2167 - TypeError: socket.on is not a function
Issue -
State: closed - Opened by lklepner over 1 year ago
- 2 comments
#2166 - [ci] cache downloaded npm dependencies
Pull Request -
State: closed - Opened by jerome-benoit over 1 year ago
- 17 comments
#2165 - [fix] ensure handleUpgrade doesn't break if socket is just a stream
Pull Request -
State: closed - Opened by pimterry over 1 year ago
- 3 comments
#2164 - `send()` method does not fatal when socket is in `CLOSING` or `CLOSED` state
Issue -
State: closed - Opened by steveluscher over 1 year ago
- 1 comment
#2163 - Concatenate small buffers
Pull Request -
State: closed - Opened by lpinca over 1 year ago
- 1 comment
#2162 - Allow http and https schemes
Pull Request -
State: closed - Opened by lpinca over 1 year ago
#2161 - Allow http(s) scheme in the WebSocket constructor
Pull Request -
State: closed - Opened by lpinca over 1 year ago
#2160 - Emit at most one event per microtask
Pull Request -
State: closed - Opened by lpinca over 1 year ago
#2159 - Dispatched events are not scheduled as tasks
Issue -
State: closed - Opened by OrKoN over 1 year ago
- 18 comments
#2158 - Incorrect Broadcast Distribution as Expected
Issue -
State: closed - Opened by mahiraltinkaya over 1 year ago
- 9 comments
#2157 - Typo in disconnected client example of `README.md`
Issue -
State: closed - Opened by joshpwrk over 1 year ago
- 3 comments
#2156 - how to use wss.clients? always undefined with 'clientTracking: true' option.
Issue -
State: closed - Opened by dorcatty over 1 year ago
- 2 comments
#2155 - Error: EACCES: permission denied
Issue -
State: closed - Opened by farr64 over 1 year ago
- 2 comments
#2154 - Socket sometimes stuck at onopen with no error
Issue -
State: closed - Opened by benzmuircroft over 1 year ago
- 30 comments
#2153 - How to handle multiple websocket connection?
Issue -
State: closed - Opened by guimilleo over 1 year ago
- 5 comments
#2152 - feat: Generate typing information for library
Pull Request -
State: closed - Opened by mastrzyz over 1 year ago
- 2 comments
#2151 - Websocket RangeError: Invalid WebSocket frame: RSV2 and RSV3 must be clear
Issue -
State: closed - Opened by smallCF over 1 year ago
- 2 comments
#2150 - Restore Hixie-76 support
Issue -
State: closed - Opened by MFlyer over 1 year ago
- 2 comments
#2149 - "ws does not work in the browser. Browser clients must use the native WebSocket object" on Node
Issue -
State: closed - Opened by david-lee over 1 year ago
- 8 comments
#2148 - WebSocket ends prematurely in chrome, results in server erroring on writes
Issue -
State: closed - Opened by ThisIsMissEm over 1 year ago
- 18 comments
#2147 - WebSocket connection to 'wss://websocket_host_name/abc' failed: Insufficient resources
Issue -
State: closed - Opened by amoljagdalepucsd over 1 year ago
- 4 comments
#2146 - [pkg] Move performance lib to optionalDependencies
Pull Request -
State: closed - Opened by nuintun over 1 year ago
- 1 comment
#2145 - mjs not export `Server`
Issue -
State: closed - Opened by wszgrcy almost 2 years ago
- 1 comment
#2144 - this.terminate(); 在哪写的 没看懂 应该是 client.terminate() 吧
Issue -
State: closed - Opened by Blizzard-liu almost 2 years ago
- 5 comments
#2143 - Silent NodeJS process termination when missing ws.on('error') handler
Issue -
State: closed - Opened by dilame almost 2 years ago
- 5 comments
#2142 - Latest benchmark results
Issue -
State: closed - Opened by ThisIsMissEm almost 2 years ago
- 3 comments
#2141 - How to choose the IP V4 used to connect ?
Issue -
State: closed - Opened by flav28 almost 2 years ago
- 1 comment
#2140 - Electron Webpack Error
Issue -
State: closed - Opened by decoderid almost 2 years ago
- 9 comments
#2139 - "Leaky connections"
Issue -
State: closed - Opened by davidhq almost 2 years ago
- 13 comments
#2138 - Make it possible to use Receiver as standalone WS parser
Issue -
State: closed - Opened by steffenstolze almost 2 years ago
- 8 comments
#2137 - Websocket does not terminate all connections when calling .close() method
Issue -
State: closed - Opened by iamisti almost 2 years ago
- 17 comments
#2135 - [Question] Websockets queue to handle connexion storm
Issue -
State: closed - Opened by jerome-benoit almost 2 years ago
- 2 comments
#2134 - How to access client IP?
Issue -
State: closed - Opened by DrCWO almost 2 years ago
- 3 comments
#2133 - Documentation does not clearly indicate the message recieved is buffer
Issue -
State: closed - Opened by madhurabindu almost 2 years ago
- 3 comments
#2132 - feat(websocket.js): compatible with the case where the return value o…
Pull Request -
State: closed - Opened by xwcoder almost 2 years ago
- 2 comments
#2131 - TypeError: One and only one of the "port", "server", or "noServer" options must be specified
Issue -
State: closed - Opened by vado369 almost 2 years ago
- 3 comments
#2130 - TypeError: One and only one of the "port", "server", or "noServer" options must be specified
Issue -
State: closed - Opened by vladyslavv-ua almost 2 years ago
- 1 comment
#2129 - Exposing 'closing' event from receiver
Pull Request -
State: closed - Opened by barsvinicius almost 2 years ago
#2128 - Adding a 'closing' event when the server starts the close handshake
Pull Request -
State: closed - Opened by barsvinicius almost 2 years ago
- 1 comment
#2127 - How to reproduce broken or "zombie" connections?
Issue -
State: closed - Opened by weary-adventurer almost 2 years ago
- 2 comments
#2126 - [fix] make test/create-websocket-stream.test.js compatible with domains
Pull Request -
State: closed - Opened by mvduin almost 2 years ago
- 1 comment
#2125 - Sec-WebSocket-Key is possible to override
Pull Request -
State: closed - Opened by gustawdaniel almost 2 years ago
- 2 comments
#2124 - create-websocket-stream.test.js fails if the domain module is loaded
Issue -
State: closed - Opened by mvduin almost 2 years ago
- 2 comments
#2123 - [feature] Add option to support late addition of headers
Pull Request -
State: closed - Opened by mvduin almost 2 years ago
- 10 comments
#2122 - [WebSocketServer] Allow to use a custom `IncomingMessage` class
Pull Request -
State: closed - Opened by vansergen almost 2 years ago
- 10 comments
#2121 - Weird behaviour when "Connection" header is omitted or does not include "Upgrade"
Issue -
State: closed - Opened by Sainan almost 2 years ago
- 4 comments
#2120 - feat: optionally allow unmasked frames from clients
Pull Request -
State: closed - Opened by jrusuarez almost 2 years ago
#2119 - Node js WebSocket (NPM ws) not returning ping response when windows application in minimize mode
Issue -
State: closed - Opened by manojgupta7755 about 2 years ago
- 5 comments
#2118 - Allow ws to provide a fallback when bundling for the browser
Pull Request -
State: closed - Opened by flashd2n about 2 years ago
#2117 - WS cannot be built for browser usage with webpack 5+
Issue -
State: closed - Opened by flashd2n about 2 years ago
- 1 comment
#2116 - Export CloseEvent, ErrorEvent, MessageEvent classes
Pull Request -
State: closed - Opened by edolix about 2 years ago
- 2 comments
#2115 - Stuck in "WebSocket is not open: readyState 0 (CONNECTING)"
Issue -
State: closed - Opened by dalegacusan about 2 years ago
- 3 comments
#2114 - 'connection' event is not triggered, therefore unable to send data to remote IP
Issue -
State: closed - Opened by dalegacusan about 2 years ago
- 2 comments
#2113 - Ws._receiver._state: 0
Issue -
State: closed - Opened by flav-code about 2 years ago
- 25 comments
#2112 - docs: add error handlers to examples, and improve error event description
Pull Request -
State: closed - Opened by dyc3 about 2 years ago
- 1 comment
#2111 - Can we send header in the response before websocket upgrade?
Issue -
State: closed - Opened by sauravlikhar about 2 years ago
- 8 comments
#2110 - Add support for buffer.isUtf8
Issue -
State: closed - Opened by JMTK about 2 years ago
- 1 comment
#2109 - Revisiting Invalid WebSocket frame: RSV1 must be clear
Issue -
State: closed - Opened by timschwab about 2 years ago
- 19 comments
#2108 - try to receiving text data but get "buffer"
Issue -
State: closed - Opened by yiguxianyun about 2 years ago
- 4 comments
#2107 - Customise how upgrade requests are made
Issue -
State: closed - Opened by DanielStarkey about 2 years ago
- 4 comments
#2106 - WebSocket does not include queryParameters in WebSocket.close() requests
Issue -
State: closed - Opened by Sebastian-Nielsen about 2 years ago
- 2 comments
#2105 - Secure Client WebSocket Connections Fail Due to `wrong version number` Errors
Issue -
State: closed - Opened by ITenthusiasm about 2 years ago
- 15 comments
#2104 - Add bufferutil as dependency
Pull Request -
State: closed - Opened by wiveezdev about 2 years ago
#2103 - Support sending raw headers
Issue -
State: closed - Opened by pimterry about 2 years ago
- 7 comments
#2102 - NOT a ws issue: I can get Apache to work as a proxy for WS (not secure) but not for WSS (secure)
Issue -
State: closed - Opened by farr64 about 2 years ago
- 1 comment
#2101 - Socket Hang Up, causing the Node server to crash.
Issue -
State: closed - Opened by KrishnaFlutura about 2 years ago
- 1 comment
#2100 - The `callback` listener is not added to the `options.server`.
Issue -
State: closed - Opened by issuefiler about 2 years ago
- 1 comment
#2099 - ws.emit() is not working
Issue -
State: closed - Opened by jenkey2011 about 2 years ago
- 2 comments
#2098 - RangeError: Invalid WebSocket frame: RSV2 and RSV3 must be clear
Issue -
State: closed - Opened by ORESoftware over 2 years ago
- 11 comments
#2097 - No way to access underlying socket?
Issue -
State: closed - Opened by ORESoftware over 2 years ago
- 1 comment
#2096 - no "open", "listen" or "listening" event
Issue -
State: closed - Opened by ORESoftware over 2 years ago
- 2 comments
#2095 - what's meaning of error reason - 2
Issue -
State: closed - Opened by alanhg over 2 years ago
- 2 comments
#2094 - socket.addEventListener('open', ...) does not fire in chrome
Issue -
State: closed - Opened by ORESoftware over 2 years ago
- 1 comment
#2093 - cannot send raw object with send()
Issue -
State: closed - Opened by ORESoftware over 2 years ago
- 2 comments
#2092 - Add support to addEventListener for object containing handleEvent
Issue -
State: closed - Opened by mattrunyon over 2 years ago
#2091 - rollup-plugin-svelte: The following packages did not export their `package.json`
Issue -
State: closed - Opened by d-velopment over 2 years ago
#2090 - Heartbeat WS is OPEN check
Pull Request -
State: closed - Opened by NicholasSmilovic over 2 years ago
- 2 comments
#2089 - Custom Header For WSS Request
Issue -
State: closed - Opened by avi0786 over 2 years ago
- 11 comments
#2088 - Allow passing in a custom createConnection function
Pull Request -
State: closed - Opened by tbn-mm over 2 years ago
- 2 comments
#2087 - in Docs: replace "%s" with .toString()
Issue -
State: closed - Opened by respectabiggle over 2 years ago
- 4 comments
#2086 - [feat] `open` event for compactibility
Issue -
State: closed - Opened by loynoir over 2 years ago
- 1 comment
#2085 - how to stream utf8 string
Issue -
State: closed - Opened by beilunyang over 2 years ago
- 2 comments
#2084 - Right-hand side of 'instanceof' is not an object at initAsClient (websocket.js:666:1)
Issue -
State: closed - Opened by SamaraApp over 2 years ago
- 7 comments
#2083 - How to extend “WebSocket class” properties in Typescript?
Issue -
State: closed - Opened by zz541843 over 2 years ago
- 3 comments
#2082 - How to differentiate between messages?
Issue -
State: closed - Opened by jason-chan8 over 2 years ago
- 1 comment
#2081 - [Query] How to add certificate options in a websocket client connecting to a websocket server on C++
Issue -
State: closed - Opened by ameeakshay over 2 years ago
- 2 comments
#2080 - [Query] Is it possible to return an error message when the websocket upgrade is rejected
Issue -
State: closed - Opened by Sid200026 over 2 years ago
- 4 comments