Skip to content
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

how to keep a connecting, it always timeout after 1 minute #66

Open
kent58909 opened this issue Apr 9, 2021 · 2 comments
Open

how to keep a connecting, it always timeout after 1 minute #66

kent58909 opened this issue Apr 9, 2021 · 2 comments
Labels

Comments

@kent58909
Copy link

it always timeout.. not proxy via nginx, only melody + gin, the same code as your example...

this pic:

image

after 1 minute, timeout, disconnect, and reconnect...

@olahol olahol added the bug label Sep 14, 2022
@CodeDing
Copy link

@kent58909 it may be caused by the client implementing by gin framework which does not set the websocket's ping handler. If the session of the melody instance sends a pingMessage to the client, but the session does not received the pongMessage as response,then the underlying network connection will be corrupted.

Advise
Try to find a solution that setting up the websocket's pingHandler in your client code which must send a pongMessage as the response to the peer.

I hope that it may be helpful for you.

@jm20122012
Copy link

I ran into this issue today. I was using the gorilla websocket client, and had to explicitly create a reader goroutine to handle the server's ping message. You can reset the read deadline in the client every time the server sends its ping message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants