How to bypass the 55 second limit (websockets burst) on heroku with gorilla/websocket?

Question

go

Deployed a simple chat to heroku https://github.com/Delgus/simple-chat
I use gorilla/websocket

The problem arises in the fact that after 55 seconds the connection is terminated (

I look at the example in heroku. it is quite complicated. they also screwed a radish there.
https:/ /devcenter.heroku.com/articles/go-websocket...

But I can't find how they bypassed the 55 second limit.The

client does not understand at all that the connection was cut off.At least this thing does not work on js

ws.onerror = function() {
        alert("WEBSOCKET SERVER DOESN'T WORK!");
    };

Therefore, I think that the implementation of reconnects on the client will not help. On the server side, I also did not find how to solve it. also with English a little bit tight (

Please help) How to bypass the limit of 55 seconds?

Answer 1

The answer here helped.
https://stackoverflow.com/questions/37696527/go-go...