socket.io
socket.io copied to clipboard
socketio
Realtime application framework (Node.JS server)
### You want to: * [x] report a *bug* * [ ] request a *feature* ### Problem Description Connection fails silently, causing headaches and hours of time spent debugging. I...
**Is your feature request related to a problem? Please describe.** Right now I want to implement certain authentication functionalities at the packet level to prevent the server from emitting events...
**Describe the bug** Currently, engine.io has @types/cookie, @types/cors and @types/node as dependencies. They should instead be devDependencies. https://github.com/socketio/engine.io/blob/7033c0ed278705b569afef0bfe470c1937d1ec38/package.json#L33-L36 This is causing my projects to take many more packages as dependencies...
**Describe the bug** Other app requests get logged with pino-http. Since the express middleware support was added in commit 24786e77c5403b1c4b5a2bc84e2af06f9187f74a, I expected to be able to log using the pino-http....
Error: Using uWS.HttpRequest / uWS.Http3Request past its request handler return is forbidden (it is stack allocated). at callback (/app/node_modules/.pnpm/[email protected]/node_modules/engine.io/build/userver.js:157:20)
I'm using Engine.IO in my application primarily as a WebSocket wrapper with a long-polling fallback to work around firewalls. My server is a Node.JS script that uses Engine.IO 6.5.0 and...
**Describe the bug** https://github.com/socketio/engine.io/commit/3144d274584ae3b96cca4e609c66c56d534f1715 This is commit has fixed the bug, but some times will still appear. **To Reproduce** There is no reproduce path , in my production env has...
**Is your feature request related to a problem? Please describe.** There is a new standard called gRPC-Web that could be used as a transport between a client (browser) and backend...
**Describe the bug** Creating HTTP/2 server mentioned in the example works well with Firefox because Firefox still uses HTTP/1.1 to connect to web server. However, chrome has implemented `CONNECT` method...
**Describe the bug** When running `socket.io` and `uNetworking/uWebSockets.js`, we sometimes get this error: ``` Error: uWS.HttpResponse must not be accessed after uWS.HttpResponse.onAborted callback, or after a successful response. See documentation...
