Invalid frame header
See original GitHub issueI emit 60 times/s, then chrome errors like this:
socket.io.min.js:1 WebSocket connection to 'ws://localhost:3030/socket.io/?EIO=3&transport=websocket&sid=hRKSQOy3Pu_8n0cjAAAH' failed: Invalid frame header
koa server errors like this:
F:\websocket server\walkers\node_modules\.npminstall\ws\0.8.0\ws\lib\Receiver.js
:386
default: srcBuffer.copy(dstBuffer, dstOffset, 0, length); break;
^
RangeError: out of range index
at RangeError (native)
at fastCopy (F:\websocket server\walkers\node_modules\.npminstall\ws\0.8.0\w
s\lib\Receiver.js:386:24)
at Receiver.add (F:\websocket server\walkers\node_modules\.npminstall\ws\0.8
.0\ws\lib\Receiver.js:86:3)
at Socket.realHandler (F:\websocket server\walkers\node_modules\.npminstall\
ws\0.8.0\ws\lib\WebSocket.js:800:20)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at readableAddChunk (_stream_readable.js:177:18)
at Socket.Readable.push (_stream_readable.js:135:10)
at TCP.onread (net.js:542:20)
how can i deal with it?please
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
How to debug 'Invalid frame header' Websocket issues with ...
From my small research, Invalid Frame Header can be generated on Websocket protocol when the server sends an empty response (message with 0...
Read more >WebSocket connection to failed: Invalid frame header #4039
It still gives me "WebSocket connection to 'ws://localhost:3000/socket.io/?EIO=4&transport=websocket&sid=u4pdcuZeebUYcuCKAAAG' failed: Invalid ...
Read more >WebSocket issues / invalid frame header (occasionally)
WebSocket issues / invalid frame header (occasionally) · 1. Open resources page · 2. Play with enable/disable resources · 3. Have a look...
Read more >Getting invalid frame header error when Proxy is used - react
Hi, We are using React to run a Chrome application that communicate to our Meteor server (1.8.3) over WSS. Our Meteor is hosted...
Read more >Websocket connection breaks with Invalid Frame Header error ...
Problem: When await websocket.send_json(result) is called twice on server, the client receives the two expected json responses through ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I was also facing same issue. Try with
npm install socket.io -save
at client side also. It works for me.That should be fixed in latest release, thanks for the heads-up.