-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
WebSocket transportMode is missing heartbeat #2403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
/cc @Loonride |
Easy to implement - https://github.com/websockets/ws#how-to-detect-and-close-broken-connections, somebody want to be a champion? |
I can do this |
Client doesn't require additional code (browser automatically sends ping) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
webpack-dev-server sends keep alive heartbeat when using
transportMode: 'ws'
, consistent with sockjs-node to keep the connection open while developing.Actual Behavior
WebSocket connection times out after a period of inactivity. A page refresh is needed to reconnect.
Create React App related issue: facebook/create-react-app#8091
For Bugs; How can we reproduce the behavior?
Use
transportMode: 'ws'
, connect to running webpack-dev-server instance, and wait for socket to timeout.Here's the RFC for ping/pong in the WebSocket spec: https://tools.ietf.org/html/rfc6455#section-5.5.2
The text was updated successfully, but these errors were encountered: