If the server doesn't do an writes or is stuck in a read you can see
this behavior.
Enabling keepalive on the connection should fix this.
On 29/01/2019 10:57, mailme...@gmail.com wrote:
I wrote a both server and client side with golang, the server side
runs on centos7, and I built client side as aar package runs at
android, but I noticed If I close android network, the server side
websocket.read not get a EOF error and it still keep hang.
What is the reason? how can I solve it, thanks in advance!
--
You received this message because you are subscribed to the Google
Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to golang-nuts+unsubscr...@googlegroups.com
<mailto:golang-nuts+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
